Explore >> Select a destination
|
You are here 
|
janik6n.net | ||
| | | | |
blog.martincostello.com
|
|
| | | | | Publishing a .NET application as a container image using the .NET SDK without needing a Dockerfile and attesting the provenance of the image with GitHub Actions. | |
| | | | |
wittchen.io
|
|
| | | | | Recently GitHub introduced really interesting feature to their service called Actions. Actions can be used for automating various tasks related to the repositories like CI, CD, testing, deployment and whatnot. The general concept is as follows: We can create so called action, which can be based on a JavaScript project or a Docker container. We can also use existing actions in the Marketplace. Next, we can create workflow in the yml file, where we define our workflow. Workflow can consist of on a job with many steps using different actions. We can also define multiple jobs, where one depends on another. Workflows can be triggered in many ways. E.g. by push, pull request, creating issue, publishing release, scheduled event or external event. | |
| | | | |
actuated.dev
|
|
| | | | | Learn how to publish container images for both Arm and Intel machines from GitHub Actions. | |
| | | | |
greg.molnar.io
|
|
| | | In this tutorial, I will show you how to use MRSK to deploy a Rails app to a VPS, run Caddy in front of the docker container to handle SSL, use a hosted database server, run Redis on the same droplet, run a worker to process background jobs | ||
