@ts-cloud/core 0.7.30 → 0.7.32

package/dist/app-database.d.ts

@@ -0,0 +1,13 @@
+import type { CloudConfig, DatabaseConfig } from './types';
+/**
+ * Resolve the application's on-box/managed database declaration.
+ *
+ * `infrastructure.appDatabase` is the ONE canonical key — every ts-cloud code
+ * path that creates the database, wires `DB_*` env, backs it up, or restores it
+ * resolves through this helper so the surface can never drift again.
+ *
+ * Backward compatibility: early configs (e.g. bughq) declared the same block as
+ * `infrastructure.compute.database`. That alias is still honored when the
+ * canonical key is absent; `appDatabase` wins when both are set.
+ */
+export declare function resolveAppDatabase(config: Pick<CloudConfig, 'infrastructure'>): DatabaseConfig | undefined;

package/dist/index.d.ts

@@ -3,6 +3,7 @@
  */
 export * from './types';
 export * from './deployment-mode';
+export * from './app-database';
 export * from './drivers';
 export * from './template-builder';
 export { validateTemplate, validateTemplateSize, validateResourceLimits, type ValidationResult, } from './template-validator';

package/dist/index.js

@@ -1100,6 +1100,10 @@ function deploymentCoexistenceError(config) {
   }
   return null;
 }
+// src/app-database.ts
+function resolveAppDatabase(config) {
+  return config.infrastructure?.appDatabase ?? config.infrastructure?.compute?.database;
+}
 // src/drivers/types.ts
 function resolveCloudProvider(config) {
   if (config.cloud?.provider)
@@ -47275,6 +47279,7 @@ export {
   resolveDashboardDomain,
   resolveCredentials,
   resolveCloudProvider,
+  resolveAppDatabase,
   resolveApp,
   requiresReplacement,
   replicaManager,

package/dist/types.d.ts

@@ -2382,6 +2382,17 @@ export interface ComputeConfig {
      * `services` array above.
      */
     managedServices?: ComputeServicesConfig;
+    /**
+     * Application database created on the box's {@link managedServices} engine
+     * (role + schema, Forge-style).
+     *
+     * @deprecated Use the canonical {@link InfrastructureConfig.appDatabase}
+     * instead — same shape, one obvious home next to the other infrastructure
+     * declarations. This alias is still honored everywhere `appDatabase` is read
+     * (see `resolveAppDatabase`) so existing configs keep working; `appDatabase`
+     * wins when both are set.
+     */
+    database?: DatabaseConfig;
     /**
      * Host firewall (UFW). When enabled, only SSH + the listed ports are open.
      * On Hetzner this complements the cloud firewall; on a bare box it's the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ts-cloud/core",
-  "version": "0.7.30",
+  "version": "0.7.32",
   "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.7.30"
+    "@ts-cloud/aws-types": "0.7.32"
   },
   "devDependencies": {
     "typescript": "^7.0.2"