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'd like to see a shortcut for process-compose process list that could be accessible as process-compose ls.
Use Case:
To allow for easier adoption from docker-compose, having a command process-compose ls would be helpful for listing running processes.
Proposed Change:
Add a new command line option ls that functions the same way as process list.
Who Benefits From The Change(s)?
People who are excited to use process-compose rather than docker-compose but have experience with docker-compose and other compose tools that use ls as a way to list running processes.
Alternative Approaches
We could make a bash alias instead.
I'd be open to submitting a PR for this if this is something that would be beneficial. I just barely discovered this repo, but am not great with go, so a little explanation or a link to documentation that describes how the app is built would be very much appreciated. :)
Thanks!
The text was updated successfully, but these errors were encountered:
Feature Request
I'd like to see a shortcut for
process-compose process list
that could be accessible asprocess-compose ls
.Use Case:
To allow for easier adoption from docker-compose, having a command
process-compose ls
would be helpful for listing running processes.Proposed Change:
Add a new command line option
ls
that functions the same way asprocess list
.Who Benefits From The Change(s)?
People who are excited to use
process-compose
rather thandocker-compose
but have experience withdocker-compose
and other compose tools that usels
as a way to list running processes.Alternative Approaches
We could make a bash alias instead.
I'd be open to submitting a PR for this if this is something that would be beneficial. I just barely discovered this repo, but am not great with go, so a little explanation or a link to documentation that describes how the app is built would be very much appreciated. :)
Thanks!
The text was updated successfully, but these errors were encountered: