docker_images
batect
Our great sponsors
| docker_images | batect | |
|---|---|---|
| 1 | 4 | |
| 177 | 687 | |
| - | - | |
| 7.2 | 0.0 | |
| about 2 months ago | 6 months ago | |
| Shell | Kotlin | |
| MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
docker_images
batect
-
Act: Run your GitHub Actions locally
https://batect.dev/ this is like Act but agnostic and public
-
Show HN: Miniboss, versatile local container management with Python
If you're dockerizing a dev environment check out batect, it's kind of like the combo of docker-compose + make (i.e. simple script running) that is really the tool we all just want: https://batect.dev/ It can easily define one-off container tasks like integration test runs with just a couple lines of config.
-
Monthly 'Shameless Self Promotion' thread - 2021/07
Earlier this year at $DAYJOB I was on a project to uplift the deployment pipelines and DevOps capabilities within the team. Today we have full Continuous Deployment, Trunk Based Development, and SlackOps. I've written a couple of articles below on the approach we took which was around heavy use of Docker and the tool Batect.
-
Docker as an Integrated Development Environment
Go the next step and run a local kubernetes cluster with kind or k3s (it will take you 30 seconds to have a k8s cluster going). IMHO the kubectl CLI is a lot more logical than docker's CLI. You can create all your local storage volumes ahead of time, create a pod that attaches to it, and then just kubectl exec into the pod vs. writing a long fiddly docker command line string (or crafting a docker-compose.yml). It's easy to adjust the pod as necessary while it runs too, like adding a service to expose ports without rerunning the container.
But if you do like the idea of docker dev environemnts, check out a tool like batect: https://github.com/batect/batect It's somewhat like if docker-compose had make-like commands you could define. Your whole dev environment and workflow can be defined in a simple yaml config that anyone can use.
What are some alternatives?
action-tmate - Debug your GitHub Actions via SSH by using tmate to get access to the runner system itself.
Docker Compose - Define and run multi-container applications with Docker
runner - The Runner for GitHub Actions :rocket:
toolbox - Tool for interactive command line environments on Linux
djinn - Source code for the Djinn CI platform
devtron - Tool integration platform for Kubernetes
act - Run your GitHub Actions locally 🚀
Komga - Media server for comics/mangas/BDs/magazines/eBooks with API and OPDS support
act-environments
workstation - Docker based portable Workstation
docker-flask-example - A production ready example Flask app that's using Docker and Docker Compose.
lunasec - LunaSec - Dependency Security Scanner that automatically notifies you about vulnerabilities like Log4Shell or node-ipc in your Pull Requests and Builds. Protect yourself in 30 seconds with the LunaTrace GitHub App: https://github.com/marketplace/lunatrace-by-lunasec/