master
branch that has the source code, and the gh-pages
branch that has the build codegit i
to setup node_modules)Test all local changes by running development -> jekyll serve
+ look at localhost:4000
When happy, then save all files, commit and push branch to branch with same name on Github
Create pull request between that branch and Master (default)
---- production build -----
NB: The _site
folder continuously regenerates itself, but you can try a manual jekyll build
command otherwise (do this on a separate branch as there have been unalterable bugs from this command earlier).
npm run deploy
(from the branch you finished working on) runs the script that deploys the _site
folder to gh-pages
branch, which is what the site is running on (must run jekyll build
or jekyll serve
first to generat _site
folder)
NB: Haven't had bugs with npm run deploy
, but if there are, then the local master branch is working and I can pull from master (the latest changes) and run npm run deploy
from there
For some reason, after every deploy to gh-pages
, Github usually re-publishes the site to up4movement.github.io
, so visiters to the site get 404 errors.
up4movement.com
in the Custom domain field and click Save. The site is up again in 2 seconds.