Deployment preparation
Current authorization covers the static official website and bilingual guides. Real product integration and product cloud deployment remain deferred. Prepared configuration and passing local tests do not establish a deployed service.
Official website
The domain is stack.agentbuff.dev, configured for the independent static website with bilingual guides under /docs/. The demo address stays empty and its links are hidden. Build an isolated combined release with bun website:package; after Cloudflare login and domain checks, upload the reviewed package using its printed configuration path. See official website configuration for the exact commands. Build and dry-run results do not establish live DNS, TLS or page acceptance.
The official website has its own Worker configuration and does not require product database, payment or model credentials. Its Chinese routes are /zh/; the domain is not used as product staging.
Product architecture
A product uses web, app and API Workers with internal service bindings and one public origin. Public Astro assets and SPA assets are separate; /api/* remains root-scoped. Neon and Hyperdrive are prepared for PostgreSQL, with fresh reads for permissions/payments. R2, business/dead-letter queues and scheduled maintenance need actual environment resources.
Each generated product resets resource names/IDs and supplies its own secrets. Development/staging/production must not share unintended data or provider credentials. Database schema upgrades are deliberate, separate from Worker deployment.
Before an authorized deployment
- Verify target environment, origins, routes and public docs/demo URLs.
- Replace placeholder account/resource IDs and configure secrets through the intended environment.
- Confirm actual schema and binding compatibility; rehearse required additive migrations separately.
- Test provider email/payment/OAuth, queue retries, private storage and recovery in a controlled environment.
- Build the correct target and review configuration checks before publishing.
- Verify real routes, language variants, ownership, downloads, callbacks and maintenance after deployment.
deploy:check validates configuration relationships but does not prove cloud resources exist. Do not run deploy, infrastructure apply or remote migrations as part of ordinary local translation checks.
Historical environment acceptance is kept in Chinese deployment documentation. The current local main preview remains at its already authorized schema level.