Custom Layout - Grouping or Sorting

[albertilagan]

Would be nice if we can define a custom group for each processes.
Or at the very least a persistent boolean flag and have those non persistent process be at the bottom of the list.

Sample 1:

Group 1
   - Process 1
   - Process 2
Group 2
   - Process 3
   - Process 4

ps: Group Name is not required a sample divider between groups is enough

Sample 2

Process 2
Process 3
Process 1 (non persistent)
Process 4 (non persistent)

Combination of both would be nice as well.

[faraonc]

This will be a nice addition. Sometimes I get confused when working with a monorepo.

[F1bonacc1]

Hi @albertilagan,

Thanks for the proposal.
In order to better understand your idea, can you please provide some of the use cases you have in mind?

This is what I have considered so far (feel free to correct any of those points):

1. Add an optional group flag to each process.
2. All the processes in each group are sorted lexicographically (or as they appear in the config.yaml?)
3. All the groups are sorted lexicographically.
4. All the processes without the new flag appear on top (or below?) of the grouped processes.

A few alternative approaches to consider:

1. Adding another group column and allowing to sort the table by any of the columns.
2. Showing the group name of the process in the process name (group) name, sorting everything lexicographically. Including processes without a group (will be at the bottom).
3. Adding another row to the table with the group name only.

[albertilagan]

Hi @albertilagan,

Thanks for the proposal. In order to better understand your idea, can you please provide some of the use cases you have in mind?

This is what I have considered so far (feel free to correct any of those points):

1. Add an optional group flag to each process.
2. All the processes in each group are sorted lexicographically (or as they appear in the config.yaml?)
3. All the groups are sorted lexicographically.
4. All the processes without the new flag appear on top (or below?) of the grouped processes.

A few alternative approaches to consider:

1. Adding another group column and allowing to sort the table by any of the columns.
2. Showing the group name of the process in the process name (group) name, sorting everything lexicographically. Including processes without a group (will be at the bottom).
3. Adding another row to the table with the group name only.

@F1bonacc1 This looks good actually. we actually don't use process-compose as is, we use it inside devenv.nix so I'm not too familiar with config.yaml

My take on this is

• sorting the process as they appear on the config would probably the easiest and solve most of our issue.
• The next addition is to introducing a { type: divider }, if it see that type=divider we create empty rows (or however you wanna introduce space/divider).
• Lastly, adding group column as you suggested.

to answer this In order to better understand your idea, can you please provide some of the use cases you have in mind?.
our use case is we have a large monorepo and have a lot of commands/processes per app.

PID	NAME	GROUP	STATUS
123	Caddy		Running
456	Redis		Running
789	Mailhog		Running
1011	Postgres		Running
--------	--------	--------	--------
1213	Proc1	Group1	Running
1415	Proc2	Group1	Disabled
--------	--------	--------	--------
1617	Proc3	Group2	Running
1819	Proc4	Group2	Disabled

or

PID	NAME	STATUS
123	Caddy	Running
456	Redis	Running
789	Mailhog	Running
1011	Postgres	Running
--------	--------	--------
1213	Proc1	Running
1415	Proc2	Disabled
--------	--------	--------
1617	Proc3	Running
1819	Proc4	Disabled

[albertilagan]

@F1bonacc1 just wanna clarify that if you want to introduce group field and have spacing automatically applied in between groups we don't need { type: divider } anymore.

so either { type: divider } or { group: <value> }, whatever you find more suitable.

[F1bonacc1]

@albertilagan, @faraonc
In v0.51.0 I added a concept of namespaces.
For now, they are only used for sorting
If there will be enough interest, I will also add the ability to filter by namespace.
If not defined the namespace will be default.

[albertilagan]

@albertilagan, @faraonc In v0.51.0 I added a concept of namespaces. For now, they are only used for sorting If there will be enough interest, I will also add the ability to filter by namespace. If not defined the namespace will be default.

Do we have an example on this feature yet?
Also I'm using devenv will it work if I do devenv update? or do we need devenv to update their process-compose reference?

How can I contribute to this? I can't figure out how to update the vendorHash. Process Compose v0.45.0

[F1bonacc1]

The vendor hash changes only when my dependencies change. They didn't change from v0.45.0 to v0.51.0.
I always update it in my default.nix

[thenonameguy]

@albertilagan, @faraonc In v0.51.0 I added a concept of namespaces. For now, they are only used for sorting If there will be enough interest, I will also add the ability to filter by namespace. If not defined the namespace will be default.

Do we have an example on this feature yet?

Also I'm using devenv will it work if I do devenv update? or do we need devenv to update their process-compose reference?

How can I contribute to this? I can't figure out how to update the vendorHash. Process Compose v0.45.0

I maintain the nixpkgs package of process-compose. A bot will usually pick the new release up and create a PR. It will land in a few days in nixpkgs master. Then you just have to update your nixpkgs lock in devenv (via devenv.yaml).

Until then you can add the flake of this github repo and use it directly (read: compile it yourself).

[albertilagan]

@albertilagan, @faraonc In v0.51.0 I added a concept of namespaces. For now, they are only used for sorting If there will be enough interest, I will also add the ability to filter by namespace. If not defined the namespace will be default.

Do we have an example on this feature yet?
Also I'm using devenv will it work if I do devenv update? or do we need devenv to update their process-compose reference?
How can I contribute to this? I can't figure out how to update the vendorHash. Process Compose v0.45.0

I maintain the nixpkgs package of process-compose. A bot will usually pick the new release up and create a PR. It will land in a few days in nixpkgs master. Then you just have to update your nixpkgs lock in devenv (via devenv.yaml).

Until then you can add the flake of this github repo and use it directly (read: compile it yourself).

@thenonameguy do we have update on this? :)

[F1bonacc1]

Hi @albertilagan,

It seems that v0.51.0 is now in master:
https://github.com/NixOS/nixpkgs/blob/e9e3f2e7362aba3ef709173d1777f0b893fc0ebf/pkgs/applications/misc/process-compose/default.nix#L11

Can you please confirm that it works for you as expected?

[albertilagan]

Hi @albertilagan,

It seems that v0.51.0 is now in master:

https://github.com/NixOS/nixpkgs/blob/e9e3f2e7362aba3ef709173d1777f0b893fc0ebf/pkgs/applications/misc/process-compose/default.nix#L11

Can you please confirm that it works for you as expected?

Yup was able to test it. Works as expected even though there's no spacing between namespaces, but I guess it's restricted by the table you're using.

That being said it would be nice if the default sort applies to namespace or atleast being to define default sort column in config.

[F1bonacc1]

Config sounds like the proper solution.
As long as no one asks for themes :)

[thenonameguy]

@albertilagan, @faraonc In v0.51.0 I added a concept of namespaces. For now, they are only used for sorting If there will be enough interest, I will also add the ability to filter by namespace. If not defined the namespace will be default.

Do we have an example on this feature yet?
Also I'm using devenv will it work if I do devenv update? or do we need devenv to update their process-compose reference?
How can I contribute to this? I can't figure out how to update the vendorHash. Process Compose v0.45.0

I maintain the nixpkgs package of process-compose. A bot will usually pick the new release up and create a PR. It will land in a few days in nixpkgs master. Then you just have to update your nixpkgs lock in devenv (via devenv.yaml).
Until then you can add the flake of this github repo and use it directly (read: compile it yourself).

@thenonameguy do we have update on this? :)

NixOS/nixpkgs@691a2ad
Better late than never :)