dew
Run everything in (Docker) containers (by efrecon)
toolship
A framework to containerize dev tools (by yapret)
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
dew
Posts with mentions or reviews of dew.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-04-17.
-
RHttp: REPL for HTTP
I've built dew for this. It "knows" about many of those apps (and where to get a container from). https://github.com/efrecon/dew. Adding a term app is usually just a matter of crafting an .env file with the necessary settings.
-
Toolship: A (More) Secure Workstation
I have written dew (https://github.com/efrecon/dew) for more or less the same purpose. I hardly keep any binary (and dependency) in my installation, they are all inside containers that I can easily dispose of at any time. The default in dew is to run them as your user. At the command prompt, instead of running, for example, kubectl xxx, I run dew kubectl xxx. It's a bit slower but provides an increased level of security.
-
You Don't Need to Rebuild Your Development Docker Image on Every Code Change
In the past few weeks, I have spent some time and released dew [0]. It helps encapsulating this kind of setups in configuration and minimising typing. dew is still evolving, but it has served me well.
[0]: https://github.com/efrecon/dew
toolship
Posts with mentions or reviews of toolship.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-09-20.
-
Toolship: A (More) Secure Workstation
No, I don't think you're missing anything, other than you'd only mount the directories you want the tool / development environment to have access to. Take for instance the `npm` command [1], it mounts `$PWD` so if you install a compromised package then it can go through the folder you're in, but it can't then go up directories and sniff around your home directory. It would also only have access to the environment variables that have been configured for the container, which in this case would also include AWS credentials.
1 - https://github.com/yapret/toolship/blob/main/src/node/functi...
What are some alternatives?
When comparing dew and toolship you can also consider the following projects:
Docker Compose - Define and run multi-container applications with Docker
dotfiles - My dotfiles. Buyer beware ;)
skaffold - Easy and Repeatable Kubernetes Development
firejail - Linux namespaces and seccomp-bpf sandbox
nix - Nix, the purely functional package manager
distrobox - Use any linux distribution inside your terminal. Enable both backward and forward compatibility with software and freedom to use whatever distribution you’re more comfortable with. Mirror available at: https://gitlab.com/89luca89/distrobox
dockerfiles - Various Dockerfiles I use on the desktop and on servers.