@o-a/cms-agent 0.1.0 → 0.1.6

package/README.md

@@ -58,7 +58,7 @@ Either way, the result is the same:
 ```
 cd my-site/vhost
 npm install
-node server.js
+npm start
 ```
 
 Visit `http://localhost:3000`. `create-site` prints a real API token to

package/dist/create-site/cli.js

@@ -17,10 +17,10 @@ try {
     console.log('Next steps:');
     console.log(`  cd ${targetArg}/vhost`);
     console.log('  npm install');
-    console.log('  node server.js');
+    console.log('  npm start');
     console.log('');
     console.log('Want to edit this site from a hosted admin while developing locally?');
-    console.log('  node server.js --tunnel');
+    console.log('  npm run tunnel');
 }
 catch (error) {
     if (error instanceof ScaffoldError) {

package/dist/create-site/generate-site.js

@@ -94,6 +94,16 @@ export function scaffoldSite(targetDir) {
         version: '0.0.0',
         private: true,
         type: 'module',
+        // "start" matters beyond convenience: several PaaS platforms
+        // auto-detect and run `npm start` by default for a Node app
+        // with no other deploy config - without this, a site pushed
+        // straight to one of those (no Dockerfile in the loop) simply
+        // wouldn't boot. "tunnel" mirrors the --tunnel flag create-site
+        // already tells the operator about in its own next-steps output.
+        scripts: {
+            start: 'node server.js',
+            tunnel: 'node server.js --tunnel',
+        },
         dependencies: {
             // Pinned exact, never a ^range - at v0.x even a minor bump
             // can be breaking (build plan's own word is "pinned").

package/dist/server-config.js

@@ -153,6 +153,20 @@ function parseCheckpointIntervalMs(value) {
 // restart, since this loads once at boot - matches the existing
 // "agent upgrade = restart" story already established for schema
 // migrations, a deliberate decision, not an accident.
+// PORT overrides site.config.json's own "port" (or its default) without
+// editing a file - the universal Node/12-factor convention, and how
+// several hosting platforms (Railway, Render, etc.) already inject the
+// port a process must bind. An invalid value is ignored, not a hard
+// failure - a stray non-numeric PORT shouldn't stop the whole site from
+// booting when the configured/default port would have worked fine.
+function resolvePort(configuredPort) {
+    const envPort = process.env.PORT;
+    if (envPort === undefined) {
+        return configuredPort;
+    }
+    const parsed = Number(envPort);
+    return Number.isInteger(parsed) && parsed >= 0 ? parsed : configuredPort;
+}
 export function loadServerConfig(siteRoot) {
     const configPath = join(siteRoot, VHOST_DIR_NAME, 'site.config.json');
     let raw;
@@ -161,7 +175,7 @@ export function loadServerConfig(siteRoot) {
     }
     catch {
         return {
-            port: DEFAULT_PORT,
+            port: resolvePort(DEFAULT_PORT),
             tokens: [],
             rateLimit: DEFAULT_RATE_LIMIT,
             trustProxy: false,
@@ -192,5 +206,5 @@ export function loadServerConfig(siteRoot) {
     const ipAllowlist = parseIpAllowlist(record.ipAllowlist);
     const checkpointIntervalMs = parseCheckpointIntervalMs(record.checkpointIntervalMs);
     const media = parseMedia(record.media);
-    return { port, tokens, rateLimit, trustProxy, ipAllowlist, checkpointIntervalMs, media };
+    return { port: resolvePort(port), tokens, rateLimit, trustProxy, ipAllowlist, checkpointIntervalMs, media };
 }

package/dist/server.js

@@ -142,7 +142,23 @@ export async function startServer(siteRoot, options = {}) {
     });
     // host: '0.0.0.0' - Fastify's own default binds 127.0.0.1 only,
     // which is unreachable from outside any container or remote host.
-    await app.listen({ port: serverConfig.port, host: '0.0.0.0' });
+    try {
+        await app.listen({ port: serverConfig.port, host: '0.0.0.0' });
+    }
+    catch (error) {
+        // A raw EADDRINUSE crash is a wall of Node internals with no
+        // indication of what to actually do about it. This is the single
+        // most likely startup failure a developer hits on their own
+        // machine (something else already using the default port) - tell
+        // them the two real ways to pick a different one instead of
+        // rethrowing Node's own stack trace.
+        if (error instanceof Error && 'code' in error && error.code === 'EADDRINUSE') {
+            console.error(`Port ${serverConfig.port} is already in use.`);
+            console.error(`Set a different port with the PORT environment variable (e.g. PORT=3001 node server.js), or "port" in vhost/site.config.json.`);
+            process.exit(1);
+        }
+        throw error;
+    }
     if (options.tunnel) {
         try {
             tunnel = await (options.startTunnel ?? startDevTunnel)(serverConfig.port);

package/package.json

@@ -1,12 +1,17 @@
 {
   "name": "@o-a/cms-agent",
-  "version": "0.1.0",
+  "version": "0.1.6",
   "type": "module",
   "publishConfig": {
     "access": "public"
   },
   "description": "Self-hosted, git-backed CMS agent, distributed as a compiled npm package.",
   "license": "SEE LICENSE IN LICENSE",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/o-a-com-au/granitecms.git"
+  },
+  "homepage": "https://github.com/o-a-com-au/granitecms",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
   "exports": {