fix(api): delay pm2 start until server has booted

pujitm · pujitm · commit 6dd9b93b8bc2 · 2025-01-12T14:12:32.000-05:00
prior to this, pm2 would mark unraid-api as started as soon as the
node process started. The Nest server wouldn't finish booting until
later. This meant unraid-api could "start", but the webgui wouldn't be
fully functional because it couldn't connect to the api yet. This was a
sucky user &amp; dev experience.
diff --git a/api/ecosystem.config.json b/api/ecosystem.config.json
@@ -7,6 +7,8 @@
             "cwd": "/usr/local/unraid-api",
             "log": "/var/log/unraid-api/unraid-api.log",
             "exec_mode": "fork",
+            "wait_ready": true,
+            "listen_timeout": 30000,
             "ignore_watch": [
                 "node_modules",
                 "src",
diff --git a/api/src/unraid-api/main.ts b/api/src/unraid-api/main.ts
@@ -48,7 +48,9 @@ export async function bootstrapNestServer(): Promise<NestFastifyApplication> {
         const result = await server.listen({ port: parseInt(PORT), host: '0.0.0.0' });
         console.log('Server listening on %s', result);
     }
-
+    if (process.send) {
+        process.send('ready');
+    }
     apiLogger.info('Nest Server is now listening');
 
     return app;
