Explore >> Select a destination

You are here

 nodogmablog.bryanhogan.net
GitHub Actions with .NET, Part 4 - Building an S3 bucket with Pulumi | no dogma blog
| | fanrongbin.com
Github Actions + fonttools ????????????? | Rongbin Fan
2.5 parsecs away

Travel
| |
| | shpota.com
Automating Website Release with Terraform, AWS, and GitHub Actions
2.0 parsecs away

Travel
| | So you've built a website, and you want to release it to the world? There are many unique ways this can be done. One of them is using AWS S3. It is simple, c...
| | davquar.it
Deploying Hugo on GitHub Pages with GitHub Actions | Davide Quaranta
1.7 parsecs away

Travel
| | 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
Deploying (infinitely-scalable) one-hour projects - Jordan Matelsky - Code, Coffee, & Cortex
12.5 parsecs away

Travel
| 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.