Support For Pre Defined Location #670
rafaScalet
started this conversation in
Ideas
Replies: 1 comment
-
to resolve this problem, I made a "compose.yml" file in the location of all my compose files and include all the other compose: # ~/DockerCompose/compose.yml
includes:
- path: ./postgres.yml
- path: ./grafana.yml So made a bind for tmux to go to the location and open lazydocker, but this isn't the best solution in my opinion. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have a directory in my system with docker compose files for a lot of tools and utils, I try to do a custom command to "up" and "down" the services from this files, but lazydocker don't understand what I want:
My idea is, in the config file, have an option to pass an array of hardcoded paths (relative or absolute, I don't know how difficult it is to do for relative paths, but I believe that for absolute paths it is easy) for lazydocker looks for projects written in the "default compose files", e.g: compose.yml, docker-compose.yaml, or with named files, so the services can be run everywhere:
or with relative paths:
Beta Was this translation helpful? Give feedback.
All reactions