astraluma / unholy Goto Github PK

Support projects that don't use Docker Compose, or any service definition system.

Honestly, this is half-aspirational. (What systems? Have you seen Kubernetes?)

But we should not be married to Docker+Compose forever.

Add an exec CLI command to have unholy just execute a thing in the devenv.

I just did pipx install unholy, and tried unholy --version to check what version I had.

PS C:\Users\puppy> unholy --version
Usage: unholy [OPTIONS] COMMAND [ARGS]...
Try 'unholy --help' for help.

Error: No such option: --version
PS C:\Users\puppy>

Docker Desktop for Mac now runs HTTP traffic through the system proxy. Which for $DAYJOB is zscaler with tls inspection.

Add the zscaler root cert to the container

Allow passing unholy new an out-of-repo Unholyfile that it uses as the basis of the local config.

It's annoying to call docker compose inside the devenv with the unholy settings.

Have unholy inject an alias/script of some kind to improve this.

Add a CLI command to complete blow away an unholy project.

Make sure it has all the appropriate confirmations.

Figure out how a user with multiple workstations should synchronize local configuration between those workstations.

Figure out how multiple Unholy users should share one server/daemon.

Support the VSCode distribution https://github.com/coder/code-server

This allows people not interested in Vim to use unholy.

There's a variety of frontends available besides Neovide. Support a few of them.

Forward git authentication other than SSH, so transports like HTTP can be used.

Allow unholy new to create a workspace and devenv without looking at or cloning a git repo

Reduce the number of non-python dependencies required by Unholy.

This should improve platform portability and reduce installation friction.

Add a compose command to the CLI to allow access to calling docker compose through unholy, without bouncing through unholy shell.

Allow the user to specify a shell

Support project-specific development environments.

If socat dies unceremoniously (computer dies, kill -9, etc), it'll leave a lockfile.

When starting the agent forward, ensure the socat lockfile is still valid.

Don't do everything as root. Create a user in the environment and use that for most commands.