orca.aws

orca aws up --email you@example.com [--stack orca] [--hostname H] [--console-hostname H] [--budget 100] [--zone us-east-2a] orca aws push [--tag T] # the project's image, to ECR orca aws register [--tag T] [register flags] <pipeline> [...] orca aws app <name> [--host H] [--port 8080] [--tag T] orca aws status orca aws down --yes

up creates or updates the stack from the template orca carries (deploy/aws/orca.yaml, in orca.aws_assets); the first time it needs --email, for the Budgets alert, and makes the database's password. push builds the project's image from a staged copy of pixi.toml, pixi.lock, bin/, pipelines/ and src/, with the project's Dockerfile.orca or else the template (deploy/project.Dockerfile), for arm64, tagged with the commit (or --tag) and latest, and pushes it to the stack's repository. register and app run on the control instance through SSM: register moves the scheduler and the UI to the image (orca-refresh) and registers each pipeline, /opt/orca/pipelines/<pipeline>, with the flags given, as orca register takes them; app runs the image's /opt/orca/bin/<name> beside the UI, at https://<host> (for console, the stack's ConsoleHostname). down deletes the stack, which fails while its buckets hold objects.

Files go to build/orca-aws/. --stack (default orca) and --region (default AWS_REGION, else the aws command's own) go anywhere.