fix for o2switch
This commit is contained in:
@@ -16,7 +16,7 @@
|
||||
3. Apply `db/schema.sql` to the MariaDB database created in cPanel.
|
||||
4. `npm install` (never with `--ignore-scripts` — Puppeteer needs its postinstall step to download Chromium).
|
||||
5. Configure the app in cPanel "Setup Node.js App", pointing its entry point at `src/server.js`. Passenger manages this process (start/stop/restart).
|
||||
6. Start the worker independently of Passenger, over SSH: `pm2 start ecosystem.config.cjs`, then `pm2 save`. Try `pm2 startup` to survive a server reboot; if that's not permitted without root on this account, fall back to a cPanel cron job every 5 minutes that runs `pm2 resurrect` (or checks `pm2 list` and restarts the app if absent) — validate which option this hosting plan actually allows once connected over SSH.
|
||||
6. Start the worker independently of Passenger, over SSH: `./node_modules/.bin/pm2 start ecosystem.config.cjs`, then `pm2 save`. Try `pm2 startup` to survive a server reboot; if that's not permitted without root on this account, fall back to a cPanel cron job every 5 minutes that runs `pm2 resurrect` (or checks `pm2 list` and restarts the app if absent) — validate which option this hosting plan actually allows once connected over SSH.
|
||||
7. Add a cPanel cron job to run the cleanup script periodically, e.g. every 15 minutes:
|
||||
`*/15 * * * * cd /home/<cpanel-user>/<app-path> && /usr/bin/node src/cleanup.js >> logs/cleanup.log 2>&1`
|
||||
(adjust the path and node binary location to match your actual account — check with `which node` over SSH).
|
||||
|
||||
Reference in New Issue
Block a user