Repo and ref per application

I might be confused, but I don’t see a possibility for assigning a Git repo and a ref per application.

Most of our applications live in separate repositories, so as far as I can tell using pm2 deploy is not a viable option?

We’re currently manually cloning all the repositories on our server and starting all the applications using an ecosystem.json that lives on the server.

Is this a use-case you might be looking into?

[codydaig]

I believe that it is designed to have 1 ecosystem.config.js per repo. I believe it is possible to do a workaround with the start file backtracking in the folder structure to another folder, but that’s not good practice. If you have separate repos, you should have separate ecosystem files.

If you really wanted to, set up a repo that contains sub repos. In the main repo you could have one ecosystem file. Again, not good practice. If you are separating your code into multiple repos, it is best practice to also separate out your deployment settings.

[codydaig]

Each application would need their own ecosystem.json file.

I have several websites that run multiple applications, all under the same folder structure. These applications use the same database models and controllers, however, I have multiple node apps running to handle different portions of the application. So, if something happens in the backend scripts that just handle data processing, it doesn’t affect the frontend website.