Yeah ok, let's just run one browser instance and one pool. I feel like I observed that, when I killed chromium in prod, pm2 noticed the abrupt loss of a child process and restarted the whole app process? which is rad? so maybe let's just trying relying on that and see how it goes |
||
|---|---|---|
| .. | ||
| allWakaValues.js | ||
| assetImage.js | ||
| graphql.js | ||
| outfitImage.js | ||
| sendFeedback.js | ||
| uploadLayerImage.js | ||
| validPetPoses.js | ||