Explore >> Select a destination
|
You are here 
|
rmoff.net | ||
| | | | |
chringel.dev
|
|
| | | | | This post shows an example workflow to automatically deploy the latest version of a Hugo website using GitHub Actions. | |
| | | | |
www.morling.dev
|
|
| | | | | As a software engineer, I like to automate tedious tasks as much as possible. The deployment of this website is no exception: it is built using the Hugo static site generator and hosted on GitHub Pages; so wouldn't it be nice if the rendered website would automatically be published whenever an update is pushed to its source code repository? | |
| | | | |
popey.com
|
|
| | | | | My blog at popey.com/blog is hosted on a Bitfolk VPS, built from the Hugo source code in a public GitHub repo. My workflow for publishing a post goes like this: ? Use whatever machine Im sat at ? Clone the repo ? Add a new page, edit until ready ? Push directly to the main branch Early on in my use of Hugo, I was manually using hugo and rsync over SSH directly on the VPS. | |
| | | | |
blog.orhun.dev
|
|
| | | FOSS ? Linux ? Programming | ||
