|
You are here |
chollinger.com | ||
| | | | |
chringel.dev
|
|
| | | | | This post shows an example workflow to automatically deploy the latest version of a Hugo website using GitHub Actions. | |
| | | | |
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. | |
| | | | |
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. | |
| | | | |
group.miletic.net
|
|
| | | Group for Apps and Services on Exascale Research Infrastructure is a research, development, and teaching unit at FIDIT + MedRi. | ||