37
Two ways to deploy a public GitHub Pages site from a private Hugo repository

Two ways to deploy a public GitHub Pages site from a private Hugo repository

5 years ago
Anonymous $9jpehmcKty

https://medium.freecodecamp.org/two-ways-to-deploy-a-public-github-pages-site-from-a-private-hugo-repository-627312ec63b9

Tools like Travis CI and Netlify offer some pretty nifty features, like seamlessly deploying your GitHub Pages site when changes are pushed to its repository. Along with a static site generator like Hugo, keeping a blog up to date is pretty painless.

I’ve used Hugo to build my site for years, but until this past week I’d never hooked up my Pages repository to any deployment service. Why? Because using a tool that built my site before deploying it seemed to require having the whole recipe in one place — and if you’re using GitHub Pages with the free version of GitHub, that place is public. That means that all my three-in-the-morning bright ideas and messy unfinished (and unfunny) drafts would be publicly available — and no amount of continuous convenience was going to convince me to do that.