{"id":21894128,"url":"https://github.com/hackgt/onboarding-2019","last_synced_at":"2026-04-11T00:33:05.386Z","repository":{"id":48740232,"uuid":"232650352","full_name":"HackGT/onboarding-2019","owner":"HackGT","description":null,"archived":false,"fork":false,"pushed_at":"2022-10-06T08:50:10.000Z","size":459,"stargazers_count":0,"open_issues_count":1,"forks_count":0,"subscribers_count":5,"default_branch":"master","last_synced_at":"2025-02-03T04:29:15.821Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"CSS","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/HackGT.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2020-01-08T20:16:05.000Z","updated_at":"2020-01-30T00:45:58.000Z","dependencies_parsed_at":"2023-01-19T10:00:59.821Z","dependency_job_id":null,"html_url":"https://github.com/HackGT/onboarding-2019","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/HackGT%2Fonboarding-2019","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/HackGT%2Fonboarding-2019/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/HackGT%2Fonboarding-2019/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/HackGT%2Fonboarding-2019/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/HackGT","download_url":"https://codeload.github.com/HackGT/onboarding-2019/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":244902928,"owners_count":20529115,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-11-28T13:19:04.065Z","updated_at":"2025-12-30T23:52:51.971Z","avatar_url":"https://github.com/HackGT.png","language":"CSS","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Sites are no longer active, reach out to Stephanie with questions\n\n# Tech Team Onboarding 2019\nWelcome to the HackGT Tech Team! Today you'll learn about our in house deployment system, [Beehive](https://github.com/HackGT/beehive) and how we make our live sites! Make sure that you have [jekyll](https://jekyllrb.com/docs/installation/) installed.\n\n## Step 0, Cloning\n\nClone the repository to your local machine by running `git clone https://github.com/HackGT/onboarding-2019.git`.\n\n## Step 1, Branching\nMake a branch of this code named with your first name. \n\nOn the command line, this can be done with the `git branch` command. For example, I would run `git branch stephanie`. Then, checkout your new branch with `git checkout \u003cbranchname\u003e`.\n\n## Step 2, Personalize your website!\n[Read the wiki](https://github.com/HackGT/live-site/wiki) to learn how to add content to your live site. Our system utilizes *blocks*. In order to edit the content in each block, edit the corresponding markdown file. Use `_event_pages` to edit the navigation of your site. You can also edit the themeing of your website (i.e. font, color, assets, etc.) using the files in `_sass` and `assets`. Look at some of the other branches for inspiration!\n\n## Step 3, View your website!\nBefore you start this step, make sure you have Jekyll installed. Jekyll will read the markup that you just wrote and convert it to a real website. To view your website as you develop, run `bundle exec jekyll serve`. This command will give you an address where the website is being hosted on (Usually `http://127.0.0.1:4000/`).\n\n## Step 4, Docker!\n[Docker](docker.com) is a container system for our applications. Each Docker container can be thought of as a lightweight virtual machine, which comes with the application and all it's dependencies built in.\n### Building\n Docker containers must first be built. The build process is where we specify how to run our application and tell Docker what dependencies to include. At the root directory of each of our repositories is a `Dockerfile`, which uses Docker-specific scripting lanaguage to define how the Docker container is built. There already is a Docker file in this repo from previous deployments, so this is just an fyi\n\n## Step 5, deployment.yaml\nAt the root of each of our applications there's a `deployment.yaml`. This contains options related to deployment into our cluster. For now, we only need to specify that our application will be listening on port `80`. This is what the `deployment.yaml` file in the repository does.\n\n## Step 5.5, Push IT!\n\nNow you're ready to get your ducks in a row and push to GitHub!\n\nAdd all the files you want to commit to the _staging area_:\n```\ngit add \u003cfile one\u003e \u003cfile two\u003e ...\n```\n\nCheck to see that all the changes you want to commit are written in green in:\n```\ngit status\n```\n\nCommit everything:\n```\ngit commit -m 'My commit message here!'\n```\n\nFinally, push:\n```\ngit push origin \u003cbranch name\u003e\n```\n\nIf your push failed, make sure your in-sync with GitHub by pulling any possibly new changes:\n```\ngit pull -r origin \u003cbranch name\u003e\n```\n\n## Step 6, Deployment\nThat's all you need to build an application in our cluster! Let's discuss deployment.\n\n\n[Beehive](https://github.com/hackgt/biodomes) is our repository for managing deployments of our applications. Each `yaml` file in the repository corresponds to an application hosted on a subdomain of `hack.gt`. For example, `registration.yaml` specifies the file to be hosted on `registration.hack.gt` and `dev/registration.yaml` specifies the application hosted on `registration.dev.hack.gt`. \n\nTo deploy your application, create a `yaml` file with your name in the `onboarding2019/` folder. This will be deployed to `\u003cyourname\u003e.onboarding2019.hack.gt`. In the yaml file, we simply specify the git url and branch of our application.\n\nCreate the file `onboarding2019/\u003cyourname\u003e.yaml` with the following content:\n```yaml\n git:\n    remote: https://github.com/HackGT/onboarding-2019.git\n    branch: \u003cbranch_you_made_earlier\u003e\n```\n\nOnce you push this file to the `Beehive` repository, `Beehive` will immediately begin deploying your website. In a few minutes, you should see it live at `\u003cyourname\u003e.onboarding2019.hack.gt`!\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fhackgt%2Fonboarding-2019","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fhackgt%2Fonboarding-2019","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fhackgt%2Fonboarding-2019/lists"}