@ts-cloud/core 0.16.44 → 0.16.46

package/dist/drivers/types.d.ts

@@ -1,5 +1,12 @@
 import type { CloudConfig, EnvironmentType, SiteConfig } from '../types';
 export type CloudProviderName = 'aws' | 'hetzner' | 'ssh';
+/**
+ * Everything `cloud.provider` accepts. Fly.io is not a {@link CloudProviderName}:
+ * it runs a container image on Machines, so it has no box for a CloudDriver to
+ * provision, ship a release to, or reach over SSH, and it deploys through
+ * `deployToFly()` instead.
+ */
+export type DeployProviderName = CloudProviderName | 'fly';
 /**
  * Exhaustive provider map. Provider-specific contract tests key off this type,
  * so adding a provider without adding its resilience coverage is a type error.
@@ -187,4 +194,4 @@ export interface DeploySiteReleaseResult {
  * is a per-machine override, not a statement of intent); the Hetzner token
  * check keeps the behaviour it always had.
  */
-export declare function resolveCloudProvider(config: CloudConfig): CloudProviderName;
+export declare function resolveCloudProvider(config: CloudConfig): DeployProviderName;

package/dist/types.d.ts

@@ -9,9 +9,12 @@ export interface CloudProviderConfig {
      * Raspberry Pi on the LAN, a colocated box, a VM from a provider ts-cloud
      * has no API driver for). Nothing is created or destroyed on your behalf;
      * see {@link SshConfig}.
+     *
+     * `'fly'` runs the app as a container image on Fly.io Machines; there is no
+     * box to provision or reach over SSH. See {@link FlyConfig}.
      * @default 'aws'
      */
-    provider?: 'aws' | 'hetzner' | 'ssh';
+    provider?: 'aws' | 'hetzner' | 'ssh' | 'fly';
     /**
      * Attach this project's sites to a box owned by ANOTHER project instead of
      * provisioning one. Set to the owner project's `project.slug` (e.g. `'stacks'`);
@@ -170,6 +173,45 @@ export interface SshHostConfig {
  * redirect a deploy to another machine. Resolution lives in one place:
  * `resolveSshSettings` in `@stacksjs/ts-cloud` (`drivers/ssh/config.ts`).
  */
+/**
+ * A Fly.io app, run as Machines from a container image.
+ *
+ * The API token comes from `FLY_API_TOKEN`, never config: it can create and
+ * destroy every Machine in the organization.
+ */
+export interface FlyConfig {
+    /** The Fly app name, unique across Fly.io. Defaults to `<project.slug>-<environment>`. */
+    app?: string;
+    /** The organization the app is created in. @default 'personal' */
+    org?: string;
+    /** Regions to run in, one Machine per region per `count`. @default ['iad'] */
+    regions?: string[];
+    /** Machines per region. @default 1 */
+    count?: number;
+    /** The port the app listens on inside the Machine. @default 3000 */
+    internalPort?: number;
+    /** A path answering 200 when the app is up, checked before traffic arrives. @default '/' */
+    healthPath?: string;
+    /** @default { cpuKind: 'shared', cpus: 1, memoryMb: 512 } */
+    vm?: {
+        cpuKind?: 'shared' | 'performance';
+        cpus?: number;
+        memoryMb?: number;
+    };
+    /**
+     * A persistent volume per Machine, for SQLite or uploads. A Fly volume
+     * attaches to one Machine, so each Machine gets its own.
+     */
+    volume?: {
+        name?: string;
+        sizeGb: number;
+        path: string;
+    };
+    /** Stop idle Machines and start them on the next request. @default false */
+    autoStop?: boolean;
+    /** Custom hostnames to request certificates for, beside `<app>.fly.dev`. */
+    hostnames?: string[];
+}
 export interface SshConfig {
     /** The hosts to deploy to. Exactly one host is supported today. Env: `TS_CLOUD_SSH_HOST`. */
     hosts: SshHostConfig[];
@@ -262,6 +304,11 @@ export interface CloudConfig {
      * provider.
      */
     ssh?: SshConfig;
+    /**
+     * Fly.io Machines (when cloud.provider is 'fly'): the app runs as a
+     * container image, deployed through the Machines API.
+     */
+    fly?: FlyConfig;
     /**
      * Object storage provider selection (AWS S3, Backblaze B2, Hetzner Object Storage).
      * Independent of `cloud.provider` — you can run compute on AWS while keeping

package/package.json

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