docker.el
docker.el copied to clipboard
Silex
Question: multiple projects with multiple docker-compose files
I work on multiple projects with multiple compose files.
project1 -> compose-p1-1.yaml, compose-p1-2.yaml project2 -> compose-p2-1.yaml, compose-p2-2.yaml
Every time I need to run compose command I have to switch to the project using projectile and then use C-c d F. Is there a way to configure compose file at the project level? Or is there a better workflow?
I think I was not able to convey the question properly. I updated the question.
Ah, good question.
@tarsius: is there a transient mechanism so we are able to store transient default settings per projectile projet?
Maybe by having projectile modify transient-values-file each time a projet changes?
No, but such functionality is planned. I just opened https://github.com/magit/transient/issues/189 to track this.
(FWIW my plans for the next few months are: Feb: personal stuff, Mar: undisclosed stuff, Apr: transient.)
Maybe by having projectile modify
transient-values-fileeach time a projet changes?
Worth a try but it might break in the future.
@noorul: I think editing a .dir-locals.el that sets transient-values to the appropriate thing should work, see the linked issue (that is, until it's directly supported by transient).
If you want to play with it give us some feedback :wink:
Is there any documentation with any example? I am looking for a sample format. It has the following value:
((docker) (magit-file-dispatch) (magit-submodule))
@tarsius @Silex Any help to understand how can one set transient-values with an example will be great.
If I had an example to give you I'd have done so.
I have more urgent things to do (e.g the magit-like process buffer when you press $), so the idea was that you try to find out how it works and build an example, see if that route works or not. Maybe it's a dead end.
(I am in a similar boat as @Silex, also busy and my tip also is just "something along those lines might work, give it a try".)