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 |
||
|---|---|---|
| .. | ||
| api | ||
| outfits | ||
| [[...slug]].tsx | ||
| _app.tsx | ||
| _document.tsx | ||