Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Instead of an S3 bucket you can use GitHub Pages. You push stuff to the upstream git repo and it gets deployed. It’s free (you have to pay for GitHub Pro if you don’t want to make the source code publicly available) and comes with Fastly CDN if I recall correctly. You just have to configure your custom domain.


I use a GitHub action to sync to an s3 bucket, works extremely well.

my update.yml:

  name: Update Website
  on:
    push:
      branches:
      - production
  jobs:
    deploy:
      runs-on: ubuntu-latest
      steps:
      - uses: actions/checkout@master
      - uses: jakejarvis/s3-sync-action@master
        with:
          args: 
        env:
          AWS_S3_BUCKET: ${{ secrets.AWS_S3_BUCKET }}
          AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
          AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
          AWS_REGION: 'myregion'
          SOURCE_DIR: 'mydir'


Just an FYI. You can now use OIDC to authenticate to AWS. This removes the need for hardcoded IDs and KEYs.


In the case of static HTML/JS/CSS, the webserver will make the source publicly available to your browser anyway, so that's not really an issue.


Use GH to push to S3 on commit. Done.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: