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
I'm more asking, does anyone manage everything through process-compose?
like I could in theory add a bunch of processes that just do docker compose run myapi or something like that.
Any downsides to that? My main goal here is to have a unified interface for the developers, so they know if they are working on something they can just call process-compose up -d myapi myvite or something like that.
I don't expect the tool to replace my docker-compose.yaml or to setup networking or so.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I have a repository where we manage some services in docker, some are just native applications (like a vite dev server for example)
I saw this issue #1 which goes way more in depth.
I'm more asking, does anyone manage everything through process-compose?
like I could in theory add a bunch of processes that just do
docker compose run myapior something like that.Any downsides to that? My main goal here is to have a unified interface for the developers, so they know if they are working on something they can just call
process-compose up -d myapi myviteor something like that.I don't expect the tool to replace my docker-compose.yaml or to setup networking or so.
Beta Was this translation helpful? Give feedback.
All reactions