spacetimedb-deploy

スター13

フォーク2

更新日2026年5月7日 20:25

Use when deploying or operating SpacetimeDB on Maincloud or self-hosted infrastructure, configuring standalone services, rotating keys, viewing logs, filtering logs, or using PGWire. Triggers on: deploy, Maincloud, self-host, standalone, systemd, Nginx, key rotation, logging, spacetime logs, PGWire, psql.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

ソース

DanMossa

DanMossa/spacetimedb-skills

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Core deployment patterns

Maincloud publish:

spacetime publish my-database --server maincloud

Maincloud clients use https://maincloud.spacetimedb.com as the URI and the database name or identity as withDatabaseName/WithDatabaseName.
Updating an existing database hot-swaps the module and runs migration checks; load database migration guidance before schema-changing deploys.
Self-hosted production should run SpacetimeDB as a dedicated user behind a reverse proxy. Keep publish/admin routes restricted unless the host is intentionally open.
Standalone mode is suitable for local development; SSL is not supported directly in standalone.
Logs can be viewed with spacetime logs <database> --follow --level info or via the HTTP logs endpoint for owners.
PGWire uses the SpacetimeDB auth token as the PostgreSQL password; treat it as a secret and avoid logging it.

Production cautions

Key rotation can invalidate tokens or cause 401/403 behavior if identity continuity is not planned.
Do not expose broad Nginx proxy rules for / unless public database creation and management are intended.
For self-hosted WebSockets, the reverse proxy must support Upgrade and Connection: Upgrade headers for /v1/database/<db>/subscribe.

Reference map

Need	Open
Maincloud deployment	references/how-to-deploy-maincloud.md
Self-hosting	references/how-to-deploy-self-hosting.md
Key rotation	references/how-to-self-hosted-key-rotation.md
Logging	references/how-to-logging.md
PGWire	references/how-to-pg-wire.md

Guidance

Be explicit about whether the target is Maincloud, local standalone, or self-hosted production.
Avoid mixing CLI publishing instructions with server installation steps unless the user needs both.
Treat key rotation and auth material as sensitive; prefer describing required configuration over exposing values.

このリポジトリの他の Skills

同じリポジトリ

spacetimedb-databases

DanMossa/spacetimedb-skills

Use when creating, developing, building, publishing, migrating, or reasoning about SpacetimeDB database modules. Covers local development, module build/publish flow, transactions, automatic migrations, incremental migrations, and the database cheat sheet. Triggers on: database module, spacetime publish, build module, migration, transaction, atomicity, developing module.

2026-06-1914

spacetimedb-reducers

DanMossa/spacetimedb-skills

Use when writing SpacetimeDB reducers, lifecycle reducers, scheduled reducers, reducer context code, table mutations, indexed lookups, reducer isolation logic, or reducer error handling. Triggers on: reducer, ReducerContext, ctx, sender, client_connected, client_disconnected, init, scheduled reducer, insert row, delete row, update row.

2026-06-1914

spacetimedb-upgrade

DanMossa/spacetimedb-skills

Use when migrating from SpacetimeDB 1.0 to 2.0 or fixing code affected by 2.0 breaking changes. Covers reducer callbacks, event tables, event type changes, subscription API, table accessor naming, database-name connections, `sender()` method, update methods, scheduled functions, private codegen, light mode, `CallReducerFlags`, and confirmed reads. Triggers on: upgrade, migrate, 1.0, 2.0, breaking changes.

2026-06-1914

spacetimedb-auth

DanMossa/spacetimedb-skills

Use when implementing SpacetimeDB authentication or authorization, including SpacetimeAuth, Auth0, Clerk, OIDC, auth claims, subject/issuer checks, custom claims, roles, row-level security, and rejecting client connections. Triggers on: auth, authentication, authorization, SpacetimeAuth, Auth0, Clerk, OIDC, claims, RLS, row-level security.

2026-05-0714

spacetimedb-cli

DanMossa/spacetimedb-skills

Use when running or explaining SpacetimeDB CLI commands and standalone configuration. Covers `spacetime init`, `build`, `publish`, `generate`, `call`, `sql`, `logs`, `describe`, `dev`, `server`, `start`, login/logout, and `config.toml`. Triggers on: spacetime CLI, spacetime publish, spacetime generate, spacetime sql, spacetime logs, spacetime server.

2026-05-0714

spacetimedb-client-c-sharp

DanMossa/spacetimedb-skills

Use when writing SpacetimeDB C# or Unity clients, generated C# bindings, connection setup, subscriptions, cache access, reducer invocation, callbacks, or identity handling. Triggers on: C#, CSharp, Unity, C# SDK, generated C# bindings, Unity SDK, C# subscription, C# reducer call.

2026-05-0714

name	spacetimedb-deploy
description	Use when deploying or operating SpacetimeDB on Maincloud or self-hosted infrastructure, configuring standalone services, rotating keys, viewing logs, filtering logs, or using PGWire. Triggers on: deploy, Maincloud, self-host, standalone, systemd, Nginx, key rotation, logging, spacetime logs, PGWire, psql.
license	MIT

Use this skill for deployment, operations, and production diagnostics.

Core deployment patterns

Maincloud publish:

spacetime publish my-database --server maincloud

Maincloud clients use https://maincloud.spacetimedb.com as the URI and the database name or identity as withDatabaseName/WithDatabaseName.
Updating an existing database hot-swaps the module and runs migration checks; load database migration guidance before schema-changing deploys.
Self-hosted production should run SpacetimeDB as a dedicated user behind a reverse proxy. Keep publish/admin routes restricted unless the host is intentionally open.
Standalone mode is suitable for local development; SSL is not supported directly in standalone.
Logs can be viewed with spacetime logs <database> --follow --level info or via the HTTP logs endpoint for owners.
PGWire uses the SpacetimeDB auth token as the PostgreSQL password; treat it as a secret and avoid logging it.

Production cautions

Key rotation can invalidate tokens or cause 401/403 behavior if identity continuity is not planned.
Do not expose broad Nginx proxy rules for / unless public database creation and management are intended.
For self-hosted WebSockets, the reverse proxy must support Upgrade and Connection: Upgrade headers for /v1/database/<db>/subscribe.

Reference map

Need	Open
Maincloud deployment	references/how-to-deploy-maincloud.md
Self-hosting	references/how-to-deploy-self-hosting.md
Key rotation	references/how-to-self-hosted-key-rotation.md
Logging	references/how-to-logging.md
PGWire	references/how-to-pg-wire.md

Guidance

Be explicit about whether the target is Maincloud, local standalone, or self-hosted production.
Avoid mixing CLI publishing instructions with server installation steps unless the user needs both.
Treat key rotation and auth material as sensitive; prefer describing required configuration over exposing values.