You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Our main monorepo has a lot of compose files (over 20), for us to easily manage our stack when we use the docker compose command we don't pass all of our compose files to the docker compose command we use the -p flag with docker compose, docker compose -p (project name) will automatically include all of our compose files.
I imagine that adding a project flag -p to the lazydocker command would be very helpful for anyone who uses lazydocker.
I've read a little bit in the lazydocker source code I imagine that I might be able to create a PR to add this feature and the end result would look like this
lazydocker - The lazier way to manage everything docker
https://github.com/jesseduffield/lazydocker
Flags:
--version Displays the program version string.
-h --help Displays help with available flag, subcommand, and positional value parameters.
-c --config Print the current default config
-d --debug a boolean
-f --file Specify alternate compose files
-p --project-name Specify docker compose project name
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Our main monorepo has a lot of compose files (over 20), for us to easily manage our stack when we use the docker compose command we don't pass all of our compose files to the docker compose command we use the
-p
flag with docker compose,docker compose -p (project name)
will automatically include all of our compose files.I imagine that adding a project flag
-p
to the lazydocker command would be very helpful for anyone who uses lazydocker.I've read a little bit in the lazydocker source code I imagine that I might be able to create a PR to add this feature and the end result would look like this
The text was updated successfully, but these errors were encountered: