overmind
skopeo
overmind | skopeo | |
---|---|---|
15 | 22 | |
2,708 | 7,402 | |
- | 2.7% | |
6.4 | 9.0 | |
27 days ago | 7 days ago | |
Go | Go | |
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.
overmind
-
Connecting Debugger to Rails Applications
Another solution is to use a different tool to drive the Procfile. The one I'm most familiar with is a tool called overmind. If you run your Procfile with overmind, you'll be able to open up a new terminal window and individually connect to any of the processes that are running. So if you want to connect to the web process to debug, you can open up a new window and run overmind connect web, and you'll have a window where you can work with the debugger's prompt.
-
Overmind, a better foreman or bin/dev for your Procfile
I recently wrote about Overmind (https://github.com/DarthSim/overmind), a drop in replacement for foreman.
If you've ever used Forman or another local Procfile/process manager, I think you'll love Overmind.
It's basically a more customisable foreman that runs in tmux - which means you can do cool things like tmux into a process and attach a debugger (which is nearly impossible with foreman).
Hope you enjoy the article!
-
Procfile.dev, bin/dev, and Rails 7 — how they work, and why (I think) they're great.
We switched to overmind and it's been great.
Hey, thanks for the comment u/sjieg! I don't have anything to add here, apart from suggesting the Overmind gem (https://github.com/DarthSim/overmind), which I just learnt about from another comment.
-
Show HN: Localias, securely manage local devserver aliases
I run an app with a bunch of separate processes managed in a Procfile invoked by Overmind (https://github.com/DarthSim/overmind):
```
app-web: cd app && poetry run invoke server
app-vite: cd app && pnpm dev
app-storybook: cd app && pnpm story:dev
api: cd api && poetry run invoke server
docs: cd docs && npm run dev
marketing: cd marketing && source .env && npm run dev
```
Maybe it's my getting older, but I've found it _infuriating_ to remember which process is bound to 3003 vs 3002 vs 3001 and so on. Very grateful for this project so I can save myself a couple seconds of frustration every day — t/y OP for building it!
-
Yew + Actix project
Use Overmind or cargo-runcc to run multiple commands in a single terminal, instead of running the server and the client in separate terminals
- Scaling Mastodon with systemd template units
-
Fly.io and Tailscale Saved Notado
FYI: Your link for Overmind is to the wrong project. The process manager is https://github.com/DarthSim/overmind
The article currently links to a deprecated Angular.js project with the same name (https://github.com/geddski/overmind)
-
Run multiple discord.py from main.py
However, as you might expect, managing that becomes a bit of a chore in the long run, this is where my recommendation of Overmind comes in.
- docker-compose without dockers
skopeo
-
A better, faster approach to downloading docker images without docker-pull: Skopeo
I decided to go searching for an alternative means to pull a docker image. In my search I discovered Skopeo, an alternative method to download Docker images that proved to be surprisingly effective. It not only downloaded the image faster, it also allowed me to save my image in a tar file, which means you can pull an image on one system and share that image to another system, loading it easily to docker instance on that system. This can be very beneficial if you have multiple systems and don't want to download an image multiple times.
-
[OC] Update: dockcheck - Checking updates for docker images without pulling - automatically update containers by choice.
But I'd suggest looking into if it's solved by other tools already, like regclient/regclient and their regsync features or something like containers/skopeo.
-
Wrapping Go CLI tools in another CLI?
Have a use case where we have a CLI (built with cobra) for our dev teams which can execute common tasks. One of those tasks we want to implement is to copy docker images from the internet to our internal registry. A tool such as skopeo can do this and much more. Instead of essentially re-writing the functionality directly into our CLI we'd like to embed it. This would also negate the need for the dev teams to manage multiple CLI tools.
-
Rails on Docker · Fly
Self hoisting here, I put this together to make it easier to generate single (extra) layer docker images without needing a docker agent, capabilities, chroot, etc: https://github.com/andrewbaxter/dinker
Caveat: it doesn't work on Fly.io. They seem to be having some issue with OCI manifests: https://github.com/containers/skopeo/issues/1881 . They're also having issues with new docker versions pushing from CI: https://community.fly.io/t/deploying-to-fly-via-github-actio... ... the timing of this post seems weird.
FWIW the article says
> create a Docker image, also known as an OCI image
I don't think this is quite right. From my investigation, Docker and OCI images are basically content addressed trees, starting with a root manifest that points to other files and their hashes (root -> images -> layers -> layer configs + files). The OCI manifests and configs are separate to Docker manifests and configs and basically Docker will support both side by side.
-
How are you building docker images for Apple M1?
skopeo is another tool worth looking into. we've started deploying amd and arm nodes into our k8s clusters, and this tool was incredibly easy to build around for getting multi-arch images into our container registry.
-
Get list of image architectures
I would use skopeo, the tool is quite handy for working with remote images. https://github.com/containers/skopeo
-
Implement DevSecOps to Secure your CI/CD pipeline
Using distroless images not only reduces the size of the container image it also reduces the surface attack. The need for container image signing is because even with the distroless images there is a chance of facing some security threats such as receiving a malicious image. We can use cosign or skopeo for container signing and verifying. You can read more about securing containers with Cosign and Distroless Images in this blog.
-
ImagePullPolicy: IfNotPresent - (image doesn’t exist in repo) - Is it possible to pull the micro service image from an EKS node and then push to repo?
Look at using tools like skopeo or crane
-
Monitoring image updates when not using :latest!
You could try some commandline tool like skopeo to fetch the image tags regularly and do some shell magic to notify you on any change you want
-
Containers without Docker (podman, buildah, and skopeo)
This is what Podman, an open-source daemonless and rootless container engine, was developed with in mind. Podman runs using the runC container runtime process, directly on the Linux kernel, and launches containers and pods as child processes. In addition, it was developed for the Docker developer, with most commands and syntax seamlessly mirroring Docker's. Buildah, an image builder, and Skopeo, the image utility tool, are both complimentary to Podman as well, and extend the range of operations able to be performed.
What are some alternatives?
Foreman - Manage Procfile-based applications
go-containerregistry - Go library and CLIs for working with container registries
docker-slim - Slim Rails images, Rails/Sidekiq/ActionCable-standalone/Nginx with Docker-Compose & Kubernetes (StatefulSet Postgres & Redis)
kaniko - Build Container Images In Kubernetes
exo - A process manager & log viewer for dev
dive - A tool for exploring each layer in a docker image
modd - A flexible developer tool that runs processes and responds to filesystem changes
sinker - A tool to sync images from one container registry to another
process-compose - Process Compose is a simple and flexible scheduler and orchestrator to manage non-containerized applications.
jib - 🏗 Build container images for your Java applications.
dip - The dip is a CLI dev–tool that provides native-like interaction with a Dockerized application.
buildkit - concurrent, cache-efficient, and Dockerfile-agnostic builder toolkit