Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feature request: Allow services to be grouped or labeled #175

Open
RyanBard opened this issue Jun 27, 2018 · 1 comment
Open

feature request: Allow services to be grouped or labeled #175

RyanBard opened this issue Jun 27, 2018 · 1 comment
Assignees

Comments

@RyanBard
Copy link

It would be nice if I could specify a groupId or label or something to be able to control multiple services (similar to "all", but defined by me) without resorting to multiple fuge shells.

Ex.

critical_service1:
  ...
  group: minimal

critical_service2:
  ...
  group: minimal

critical_service3:
  ...
  group: minimal

service1:
  ...
  group: optional

service2:
  ...
  group: optional
start all
...
stop optional
...
stop all
...
start minimal

Some of my microservices consume more resources at rest than I would like and aren't always needed, so it would be nice to be able to manage my resources easily instead of defining multiple yml files and having to manage things in multiple fuge shells.

@pelger
Copy link
Contributor

pelger commented Jul 13, 2018

Yep that's one we've been thinking about. Currently we're using multiple fuge shells as well on on system where we have some node processes and some Java, the Java processes are slow to start so we split the configuration. +1 will get some time on this soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants