@rip-lang/server 0.8.2 → 1.0.0

package/README.md

@@ -2,28 +2,32 @@
 
 # Rip Server - @rip-lang/server
 
-> **Pure Rip application server — multi-worker, hot reload, HTTPS, mDNS**
+> **A production-grade application server with multi-worker processes, hot reload, HTTPS, and mDNS — written entirely in Rip**
 
-## Overview
+Rip Server is a self-contained application server that turns any
+[@rip-lang/api](https://github.com/shreeve/rip-lang/tree/main/packages/api)
+app into a production-ready service. It handles multi-worker process management,
+rolling restarts, automatic TLS certificates, mDNS service discovery, and
+request load balancing — all in a single 1,200-line file with zero external
+dependencies.
 
-`@rip-lang/server` is a production-grade application server written entirely in Rip. It provides multi-worker process management, hot reloading, automatic HTTPS, and mDNS service discovery — all in a single ~1,200 line file.
+## Features
 
-- **`server.rip`** (~1,200 lines) — Complete server: CLI, workers, load balancing, TLS, mDNS
-
-**Core Philosophy**: Application servers should be simple, fast, and reliable. No complex configuration files. No dependency on external process managers. Just run your app.
-
-### Key Features
-
-- **Multi-Worker Architecture** — Automatic worker spawning based on CPU cores
-- **Hot Module Reloading** — File-watch based reloading in development
-- **Directory Watching** — Watch all `.rip` files with `-w` flag for instant reload
-- **Rolling Restarts** — Zero-downtime deployments
+- **Multi-worker architecture** — Automatic worker spawning based on CPU cores
+- **Hot module reloading** — File-watch based reloading with `-w` flag
+- **Rolling restarts** — Zero-downtime deployments
 - **Automatic HTTPS** — TLS with mkcert or self-signed certificates
-- **mDNS Discovery** — `.local` hostname advertisement
-- **Request Queue** — Built-in request buffering and load balancing
-- **CLI Interface** — Simple command-line operation
+- **mDNS discovery** — `.local` hostname advertisement
+- **Request queue** — Built-in request buffering and load balancing
+- **Built-in dashboard** — Server status UI at `rip.local`
+- **Powered by @rip-lang/api** — Runs any Rip API app
+
+| File | Lines | Role |
+|------|-------|------|
+| `server.rip` | ~1,210 | Complete server: CLI, workers, load balancing, TLS, mDNS |
+| `server.html` | ~420 | Built-in dashboard UI |
 
-> **See Also**: For the API framework, see [@rip-lang/api](../api/README.md).
+> **See Also**: For the API framework, see [@rip-lang/api](../api/README.md). For the DuckDB server, see [@rip-lang/db](../db/README.md).
 
 ## Quick Start
 
@@ -424,8 +428,8 @@ Most settings are configured via CLI flags, but environment variables provide an
 | `RIP_MAX_REQUESTS` | `r:N,...` | `10000` | Max requests before worker recycle |
 | `RIP_MAX_SECONDS` | `r:...,Ns` | `3600` | Max seconds before worker recycle |
 | `RIP_MAX_QUEUE` | `--max-queue=` | `512` | Request queue limit |
-| `RIP_QUEUE_TIMEOUT_MS` | `--queue-timeout-ms=` | `2000` | Queue wait timeout (ms) |
-| `RIP_CONNECT_TIMEOUT_MS` | `--connect-timeout-ms=` | `20000` | Worker request timeout (ms) |
+| `RIP_QUEUE_TIMEOUT_MS` | `--queue-timeout-ms=` | `30000` | Queue wait timeout (ms) |
+| `RIP_CONNECT_TIMEOUT_MS` | `--connect-timeout-ms=` | `2000` | Reserved for future use |
 | `RIP_READ_TIMEOUT_MS` | `--read-timeout-ms=` | `30000` | Worker read timeout (ms) |
 
 ## Dashboard

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rip-lang/server",
-  "version": "0.8.2",
+  "version": "1.0.0",
   "description": "Pure Rip application server — multi-worker, hot reload, HTTPS, mDNS",
   "type": "module",
   "main": "server.rip",
@@ -37,6 +37,10 @@
   },
   "author": "Steve Shreeve <steve.shreeve@gmail.com>",
   "license": "MIT",
+  "dependencies": {
+    "rip-lang": "^2.9.0",
+    "@rip-lang/api": "workspace:*"
+  },
   "files": [
     "bin/",
     "server.rip",

package/server.rip

@@ -340,8 +340,8 @@ parseFlags = (argv) ->
     reload
     socketPrefix
     maxQueue: coerceInt(getKV('--max-queue='), coerceInt(process.env.RIP_MAX_QUEUE, 512))
-    queueTimeoutMs: coerceInt(getKV('--queue-timeout-ms='), coerceInt(process.env.RIP_QUEUE_TIMEOUT_MS, 2000))
-    connectTimeoutMs: coerceInt(getKV('--connect-timeout-ms='), coerceInt(process.env.RIP_CONNECT_TIMEOUT_MS, 20000))
+    queueTimeoutMs: coerceInt(getKV('--queue-timeout-ms='), coerceInt(process.env.RIP_QUEUE_TIMEOUT_MS, 30000))
+    connectTimeoutMs: coerceInt(getKV('--connect-timeout-ms='), coerceInt(process.env.RIP_CONNECT_TIMEOUT_MS, 2000))
     readTimeoutMs: coerceInt(getKV('--read-timeout-ms='), coerceInt(process.env.RIP_READ_TIMEOUT_MS, 30000))
     jsonLogging: has('--json-logging')
     accessLog: not has('--no-access-log')
@@ -876,20 +876,15 @@ class Server
   forwardOnce: (req, socketPath) ->
     inUrl = new URL(req.url)
     forwardUrl = "http://localhost#{inUrl.pathname}#{inUrl.search}"
-    controller = new AbortController()
-    connectTimer = setTimeout (-> controller.abort()), @flags.connectTimeoutMs
     readTimeoutMs = @flags.readTimeoutMs
 
     try
-      # Don't await fetch - we need to race the promise against timeout
-      fetchPromise = fetch(forwardUrl, { method: req.method, headers: req.headers, body: req.body, unix: socketPath, signal: controller.signal })
+      fetchPromise = fetch(forwardUrl, { method: req.method, headers: req.headers, body: req.body, unix: socketPath })
       readGuard = new Promise (_, rej) ->
         setTimeout (-> rej(new Error('Upstream timeout'))), readTimeoutMs
       res = Promise.race!([fetchPromise, readGuard])
-      clearTimeout(connectTimer)
       res
     catch err
-      clearTimeout(connectTimer)
       if err.message is 'Upstream timeout'
         return new Response('Gateway timeout', { status: 504 })
       throw err