@rip-lang/server 1.3.34 → 1.3.35

package/README.md

@@ -1037,13 +1037,27 @@ migrations, table creation, and seeding.
 export setup = ->
   await createTables()
   await seedData()
-  console.log 'Database ready'
+  p 'Database ready'
 ```
 
 The setup function can export as `setup` or `default`. If the file doesn't
 exist, the setup phase is skipped entirely (no overhead). If setup fails,
 the server exits immediately.
 
+When `setup.rip` is present, the `rip-server: https://...` URL lines are
+**suppressed at the top** of the output — they will appear later via `[setup]`
+instead, after migrations complete. The actual server URLs are passed to the
+setup process as `process.env.RIP_URLS` (comma-separated), so you can display
+them exactly as rip-server computed them:
+
+```coffee
+# setup.rip — print URLs at the bottom after setup completes
+export setup = ->
+  await runMigrations()
+  urls = process.env.RIP_URLS?.split(',') or []
+  p "[setup] #{urls.join(' | ')}"
+```
+
 ## Environment Variables
 
 Most settings are configured via CLI flags, but environment variables provide an alternative for containers, CI/CD, or system-wide defaults.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rip-lang/server",
-  "version": "1.3.34",
+  "version": "1.3.35",
   "description": "Pure Rip web framework and application server",
   "type": "module",
   "main": "api.rip",
@@ -45,7 +45,7 @@
   "author": "Steve Shreeve <steve.shreeve@gmail.com>",
   "license": "MIT",
   "dependencies": {
-    "rip-lang": ">=3.13.51"
+    "rip-lang": ">=3.13.52"
   },
   "files": [
     "api.rip",