scarr VS gh-pages

A while back I wrote a tool* to make this as easy as possible for my use case: a single command to register the domain, jump through all the AWS hoops, and have a live static site with ssl at the end. I was pretty happy with it.

These days, though, I just use netlify. It's not quite one command, but it's about heroku-level easy, and it gives you a lot of little niceties (autodeploy whenever you push a specific git branch to github, ssl, etc).

* https://github.com/kkuchta/scarr

1) First setup GitHub Pages on the GitHub quickstart 2) Install gh-pages package. It can be installed to devDependencies. NPM

I think this is what you're looking for: https://www.npmjs.com/package/gh-pages and then scroll towards the bottom, and you can set it up to run using a script in your package.json file using npm run deploy

After that I turned to a package called gh-pages, which pushed the bundled files to a new branch and deployed the Github Pages website from there, and I gave it a try.

To automate this process, there is an npm package called gh-pages. It enables you to deploy your new version of the build, which is inside the dist folder for Svelte projects, to a new branch. Then if you configure your GitHub page to deploy that branch, this would automatically be deployed.

Generate App: this action aims to build and copy the React web application inside your repository and publish it using gh-pages NPM tool.

It will create a branch named gh-pages and (after a few steps that I’ll go through in the next section) automatically update that branch with new files whenever you run npm run deploy. If you want the details on everything going on behind the scenes here, check out the gh-pages docs.

I had this too, its a bug with Github... the fix is listed here about half way down: https://github.com/tschaub/gh-pages/issues/213

GitHub pages are pretty nifty. The https://github.com/tschaub/gh-pages package complements it nicely for those wiching for a stronger local development experience.