batect
action-tmate
Our great sponsors
batect | action-tmate | |
---|---|---|
4 | 13 | |
687 | 2,652 | |
- | - | |
0.0 | 5.5 | |
6 months ago | 14 days ago | |
Kotlin | JavaScript | |
Apache License 2.0 | MIT License |
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.
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.
action-tmate
-
How to debug GitHub actions. Real-world example
The go-to method of debugging GitHub Actions is tmate. With tmate we can connect to our running Action terminal and see what is going on there by executing some simple commands!
-
GitHub Actions Are a Problem
In addition to the suggestions others have made for locally testing workflows, there are also reverse shell actions[0] that can be used for troubleshooting CI failures on the GH runners themselves.
[0] https://github.com/mxschmitt/action-tmate
-
GitHub Actions could be so much better
Been through that git commit; git push; repeat cycle too much as well until i discovered https://github.com/mxschmitt/action-tmate which gives a shell in between steps, which does not help with all problems but sure it's makes it less painful at times.
- How do you debug CI/CD pipelines? Breakpoints?
-
How easy is it to troubleshoot GHA workflows?
In addition to everything here, I also will set up https://github.com/mxschmitt/action-tmate when Iām debugging. It helps tremendously since you can temporarily access the server.
-
Act: Run your GitHub Actions locally
Unfortunately act is only capable of running very simple workflows. I've found this action to be more useful against the endless PR stream: https://github.com/mxschmitt/action-tmate
You drop it in your workflow and get an SSH shell into the worker, figure things out iteratively, then push when it's working.
-
CI/CD using GitHub Actions for Rails and Docker
Solution: Tip o' the hat to Daniela Baron here, there's a real life saver of tool call tmate.
-
Hosting VMs on GitHub Actions?
Here's a recent case where users of tmate - which lets you SSH into an actions worker - reported problems: https://github.com/mxschmitt/action-tmate/issues/104
-
Github actions error while pushing code to package registry
see: https://github.com/mxschmitt/action-tmate
-
Work with GitHub Actions in Your Terminal with GitHub CLI
Thought I'd get their docs updated - https://github.com/mxschmitt/action-tmate#manually-triggered...
What are some alternatives?
Docker Compose - Define and run multi-container applications with Docker
reverse-rdp-windows-github-actions - Reverse Remote Desktop into Windows on GitHub Actions for Debugging and/or Job Introspection [GET https://api.github.com/repos/nelsonjchen/reverse-rdp-windows-github-actions: 403 - Repository access blocked]
toolbox - Tool for interactive command line environments on Linux
act - Run your GitHub Actions locally š
devtron - Tool integration platform for Kubernetes
floatly - An extension that adds a floating button for browser quick actions
Komga - Media server for comics/mangas/BDs/magazines/eBooks with API and OPDS support
mongodb-github-action - Use MongoDB in GitHub Actions
workstation - Docker based portable Workstation
github-activity-readme - Updates README with the recent GitHub activity of a user
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/
ssh-agent - GitHub Action to setup `ssh-agent` with a private key