rocky installable via PM2 about rocky

[h2non]

Thanks for the proposal.

Sounds good to me. After a brief reading of the PM2 docs, I believe that I best fit is creating another package specifically for PM2 ecosystem, e.g: pm2-rocky.

I would prefer keeping rocky repository agnostic of any specific non-mandatory tool, but I'm totally open to provide and simplify the ways that people can use it with a specific handy tool.

I'll analyze in detail the PM2 modules and how to build a proper module wrapper for rocky.

[Unitech]

Sure keep rocky as a module name it's perfect!

You can already install rocky like that:

$ pm2 install rocky

Now the problem is how to configure rocky easily, I will have a look on how to point rocky to a specified TOML file

[h2non]

Perfect.

Regarding to the TOML configuration, I'll consider supporting two additional ways to load the config:

• Reading it from stdin
• Auto discovering the file looking in the cwd and walk up ancester's dirs until find a rocky.toml file.

This should mitigate the CLI overhead. Sounds good for the PM2 integration as well?

[h2non]

I'm taking a look to the PM2 docs in order to find a proper way to configure rocky without too much pain.

Since rocky will be mostly consumed from CLI from PM2, I think the proper way to do this is passing it via args config, or even via environment variable like ROCKY_CONFIG, pointing to the config file path.

Do you see another more convenient way to integrate rocky?