@ts-cloud/core 0.5.26 → 0.5.28

package/dist/index.js

@@ -22347,6 +22347,21 @@ function resolveManagementDashboardSite(config, environment, opts) {
   const domain = resolveDashboardDomain(config, environment, opts.domain);
   if (!domain)
     return null;
+  const auth2 = opts.password ? { auth: { username: opts.username || "admin", password: opts.password, realm: opts.realm } } : {};
+  if (opts.live) {
+    const port = opts.port ?? 7676;
+    const site2 = {
+      root: opts.uiRoot,
+      deploy: "server",
+      domain,
+      start: `cloud dashboard:serve --box --host 127.0.0.1 --port ${port}`,
+      port,
+      ssl: { provider: "letsencrypt" },
+      ...opts.build === false || opts.build === undefined ? {} : { build: opts.build },
+      ...auth2
+    };
+    return { name: "dashboard", site: site2 };
+  }
   const site = {
     root: opts.uiRoot,
     deploy: "server",
@@ -22354,7 +22369,7 @@ function resolveManagementDashboardSite(config, environment, opts) {
     domain,
     ssl: { provider: "letsencrypt" },
     ...opts.build === false || opts.build === undefined ? {} : { build: opts.build },
-    ...opts.password ? { auth: { username: opts.username || "admin", password: opts.password, realm: opts.realm } } : {}
+    ...auth2
   };
   return { name: "dashboard", site };
 }

package/dist/presets/management-dashboard.d.ts

@@ -24,6 +24,15 @@ export interface ManagementDashboardOptions {
     password?: string;
     /** Browser auth realm. */
     realm?: string;
+    /**
+     * Live mode: deploy the dashboard as a server-app (a `cloud dashboard:serve
+     * --box` service on the box) instead of static files, so it serves the
+     * project's LIVE data + a working control API on the server. The proxy routes
+     * the dashboard host to its loopback port (behind Basic auth).
+     */
+    live?: boolean;
+    /** Loopback port for the live (box-mode) dashboard service. @default 7676 */
+    port?: number;
 }
 /**
  * Derive a dashboard hostname (`dashboard.<apex>`) from the project's configured

package/dist/types.d.ts

@@ -744,17 +744,43 @@ export interface SiteCacheConfig {
     /** Front this origin with a CDN (CloudFront on AWS; advisory on Hetzner). */
     cdn?: boolean;
 }
+/**
+ * A redirect-only site target: the gateway answers the site's `domain` with an
+ * HTTP redirect to `to`, appending the request path + query by default so deep
+ * links survive.
+ */
+export interface SiteRedirectConfig {
+    /** Target base URL, e.g. `https://verygoodadblock.org` (a path prefix is allowed). */
+    to: string;
+    /** HTTP status. Default `301` (permanent). */
+    status?: 301 | 302 | 307 | 308;
+    /** Append the request path + query to `to`. Default `true`. */
+    preservePath?: boolean;
+}
 export interface SiteConfig {
     /**
      * Directory to deploy.
      *  - For static sites: the built static files to upload to S3 (e.g., 'dist').
      *  - For SSR sites: the build output to tar+ship to EC2 (e.g., '.output').
+     *
+     * Optional: a redirect-only site (see {@link redirect}) ships nothing and so
+     * needs no `root`.
      */
-    root: string;
+    root?: string;
     /** Path prefix for deployment (usually '/') */
     path?: string;
     /** Custom domain for the site (e.g., 'stage.easyotc.com') */
     domain?: string;
+    /**
+     * Make this a **redirect-only site**: the reverse-proxy gateway answers this
+     * site's `domain` with an HTTP redirect to the target instead of deploying any
+     * app or static files. Use it to point an alternate/parked domain at its
+     * canonical host (e.g. `very-good-adblock.org` → `https://verygoodadblock.org`),
+     * just like a Forge "Redirect" site. Requires `domain`; `root`/`start` are not
+     * needed and are ignored. A bare string is shorthand for a permanent (301),
+     * path-preserving redirect.
+     */
+    redirect?: string | SiteRedirectConfig;
     /**
      * S3 bucket name. Default: `{slug}-{environment}-site` for `main`,
      * else `{slug}-{environment}-{siteKey}`.
@@ -2472,6 +2498,15 @@ export interface ComputeProxyConfig {
     onDemandTls?: boolean;
     /** Contact email for the ACME account when {@link onDemandTls} is enabled. */
     onDemandTlsEmail?: string;
+    /**
+     * Webroot the gateway serves ACME http-01 challenge tokens from on `:80` (and
+     * that the deploy-time issuance + renewal cron write tokens into). Only used
+     * when {@link onDemandTls} is enabled, where ts-cloud also installs a daily
+     * `tlsx acme:renew` timer so certs for every routed domain are issued on deploy
+     * and renewed before expiry — with no downtime (the running gateway answers the
+     * challenge). @default '/var/www/acme-challenge'
+     */
+    acmeWebroot?: string;
     /**
      * Put a CDN (CloudFront) in front of this self-hosted gateway. A CDN custom
      * origin can't be a bare IP and can't be one of the public aliases (it would

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ts-cloud/core",
-  "version": "0.5.26",
+  "version": "0.5.28",
   "type": "module",
   "description": "Core CloudFormation generation library for ts-cloud",
   "author": "Chris Breuer <chris@stacksjs.com>",
@@ -31,7 +31,7 @@
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {
-    "@ts-cloud/aws-types": "0.5.26"
+    "@ts-cloud/aws-types": "0.5.28"
   },
   "devDependencies": {
     "typescript": "^5.9.3"