|
You are here |
chringel.dev | ||
| | | | |
blog.railway.com
|
|
| | | | | Github Actions come with a pretty neat set of features to automate your workflows. In this post, we talk about using Github Actions to automate your deployments on Railway. | |
| | | | |
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. | |
| | | | |
zelig880.com
|
|
| | | | | Learn how to setup CI/CD and deploy your VitePress documentation site on GitHub Pages using GitHub actions. | |
| | | | |
greg.molnar.io
|
|
| | | Since Kamal 2 can host multiple sites on the same server, I am consolidating my apps into larger hosts so I have less servers to worry about. Most of my apps are Rails apps, but I have a few static jekyll sites like this blog and I decided to look into how could I move this site to a server I host other Rails apps on. | ||