Explore >> Select a destination
|
You are here 
|
chrispeoples.com | ||
| | | | |
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. | |
| | | | |
davquar.it
|
|
| | | | | A GitHub Action is the automatic execution of a job, after a specified trigger on a GitHub repository. For example, let's say that we want to run a linter on each new commit, we can create a GitHub action to do it. In this post we'll see a workflow to automatically deploy a Hugo site on GitHub Pages. | |
| | | | |
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? | |
| | | | |
laihoconsulting.com
|
|
| | | Website and personal blog of Pekka Laiho, software engineer and financial enthusiast. | ||
