{"id":18607373,"url":"https://github.com/addono/deploying-from-source","last_synced_at":"2026-01-24T20:18:29.958Z","repository":{"id":82276922,"uuid":"605924216","full_name":"Addono/deploying-from-source","owner":"Addono","description":"Hands-on demo instructions accompanying the talk \"Outsource Your Continuous Delivery Pipeline by Deploying Directly from Source-Code\"","archived":false,"fork":false,"pushed_at":"2023-03-22T14:54:15.000Z","size":416,"stargazers_count":3,"open_issues_count":0,"forks_count":0,"subscribers_count":2,"default_branch":"main","last_synced_at":"2025-05-16T21:12:18.707Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":null,"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/Addono.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,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2023-02-24T07:39:41.000Z","updated_at":"2023-02-24T12:18:47.000Z","dependencies_parsed_at":null,"dependency_job_id":"6643a07b-254c-4988-8f8a-52b9573a6711","html_url":"https://github.com/Addono/deploying-from-source","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/Addono/deploying-from-source","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Addono%2Fdeploying-from-source","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Addono%2Fdeploying-from-source/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Addono%2Fdeploying-from-source/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Addono%2Fdeploying-from-source/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/Addono","download_url":"https://codeload.github.com/Addono/deploying-from-source/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Addono%2Fdeploying-from-source/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":28736503,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-01-24T19:23:36.361Z","status":"ssl_error","status_checked_at":"2026-01-24T19:23:28.966Z","response_time":89,"last_error":"SSL_read: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"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-07T02:29:14.957Z","updated_at":"2026-01-24T20:18:29.937Z","avatar_url":"https://github.com/Addono.png","language":null,"readme":"# Deploying From Source\n\n## Modern web-app\n\nFor this exercise, we will be deploying a semi-static web-app directly from our source-control in GitHub to various providers.\nThe application we will be deploying is an alternative UI for [Hacker News](https://news.ycombinator.com/).\n\n![Screenshot](./imgs/hn-netlify.png)\n\nIn this demo, we will be deploying to the following providers. Based on how fast you are, you can pick as many as you want:\n\n- [Vercel](https://vercel.com)\n- [Netlify](https://netlify.com)\n- [AWS Amplify](https://aws.amazon.com/amplify/)\n\n### Deploying\n\n1. Fork the [`nextjs-hackernews` repo](https://github.com/Addono/nextjs-hackernews)\n2. Setup deployment from GitHub\n\n   - **Vercel**\n\n     1. Login or register at https://vercel.com\n     2. “Add new …” \u003e “Project” \u003e “Import from Git” \u003e Select forked repo from GitHub\n\n   - **Netlify**\n\n     1. Login or register at https://app.netlify.com/\n     2. “Add new site” \u003e “Import an existing project” \u003e “GitHub” \u003e Select forked repo\n\n   - **AWS Amplify**\n\n     1. Login to AWS Console\n     2. Navigate to AWS Amplify page (easiest to use the search bar at the top)\n     3. “Get Started” \u003e “Host a web-app” \u003e “GitHub” \u003e Select forked repo \u003e Click “Next” on all defaults \u003e “Safe and deploy”\n     4. (After you’re done) Delete the Amplify App\n\n3. _(Optional)_ Configure a custom domain\n\n   - **Vercel**\n\n     1. Open the settings of your site, it will be under `https://vercel.com/{USERNAME}/nextjs-hackernews/settings`.\n     2. In the left-hand panel select \"Domains\", then add a domain through the form. You can pick either one you control yourself, or pick a `somethingyouwant.vercel.app`. For your own domains, you will have to follow the instructions to configure correct DNS entries.\n\n   - **Netlify**\n\n     1. Go to \"Site settings\" \u003e \"Domain management\" \u003e \"Domains\"\n     2. Either change the `somethingyouwant.netlify.app` domain which is already configured, or add a new custom domain you manage yourself.\n\n   - **AWS Amplify**\n\n     1. Go to \"App settings\" \u003e \"Domain management\" and click \"Add domain\"\n     2. Select a domain or subdomain you want\n     3. Follow the instructions on setting up the DNS configuration, if you're using a domain which is already in Route53 then AWS will be able to do this for you.\n\n### Evaluation\n\nLet's see what we now have:\n\n- **User experience and features**\n\n  - Start by clicking around the website a bit.\n  - Open up the network console to see what's happening under the hood.\n  - Go to `/api/hello` as an example of how besides just a static-site deployment we also have deployed server-side logic.\n\n- **Developer experience**. What would the development flow look like?\n\n  The default behaviour will differ a bit between vendors:\n\n  - **Vercel** will deploy every branch and commit\n  - **Netlify** every PR\n  - **AWS Amplify** only your default branch, so in most cases either `master` or `main`. _(With additional configuration Amplify can also deploy on every branch.)_\n\n  Let's see what we got out of the box and make some change to the application:\n\n  1. Let's make some small change - e.g. change the title in [`./components/SiteHeader.js:14`](https://github.com/Addono/nextjs-hackernews/blob/9fd6baf1b6c4dfea2186b0b21d7eab1868c8b809/components/SiteHeader.js#L14) and commit that in a new branch.\n  2. Create a pull-request against the `main`-branch of **your own** fork.\n  3. Observe the GitHub integration doing it's work in the comments of your PR.\n  4. Merge in your PR and see how long it takes for your changes to propegate.\n\n- **Performance comparison**\n  - Let's look into some global latency characteristics of our website, the following tool will measure the request duration from various points across the globe: https://tools.bunny.net/http-test. Try to see if you can pick up on:\n    - Cache misses / Cold starts\n    - Deployment region: Can you see from the request duration one location all requests go to?\n  - For reference, compare your deployments to:\n    - [news.ycombinator.com](https://tools.bunny.net/http-test?query=https://news.ycombinator.com/)\n    - [hacker-news.firebaseio.com](https://tools.bunny.net/http-test?query=https://hacker-news.firebaseio.com)\n\n\u003c!--\n    - But, does this actually matter? Most browser's come with build-in website performance checking tools. In Chrome that would be Lighthouse.\n      - To open Lighthouse in Chrome: \"Options\" \u003e \"More Tools\" \u003e \"Developer Tools\" \u003e \"Lighthouse\"\n      - Run a test by clicking \"Analyze page load\"\n--\u003e\n\n\u003e Ready for another challenge? Next up, there's [instructions](./redwood-app.md) on how to deploy a Redwood app as a container to Fly.io.\n","funding_links":[],"categories":[],"sub_categories":[],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Faddono%2Fdeploying-from-source","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Faddono%2Fdeploying-from-source","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Faddono%2Fdeploying-from-source/lists"}