/explore
|
You are here 
|
til.simonwillison.net | ||
| | | | |
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. |
|
| | | | | ||
| | | | |
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. |
|
| | | | | ||
| | | | |
andrewlester.net
Deploying a SvelteKit application to GitHub Pages. |
|
| | | | | ||
| | | | |
humberto.io
Create your first static website using Pelican and hosting at GitHub Pages using Travis-CI to automate the deploy process |
|
| | | |||
