Explore >> Select a destination
|
You are here 
|
andrewlester.net | ||
| | | | |
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? | |
| | | | |
group.miletic.net
|
|
| | | | | Group for Apps and Services on Exascale Research Infrastructure is a research, development, and teaching unit at FIDIT + MedRi. | |
| | | | |
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. | |
| | | | |
blog.jordan.matelsky.com
|
|
| | | I often write silly little one-hour projects, and I want to put them online for others to enjoy. Importantly, I don't want these projects to cost me much. (I write way too many one-off projects for that!) So provisioning little virtual machines for each project is a non-starter. And while the right answer is probably to own one virtual machine and have all my projects share tenancy on it, I've had a few one-hour projects that actually gained some traction and needed some scalability built in. | ||
