Functions deploy as part of your project. This page covers the deploy flow — staging, production, rollbacks.Documentation Index
Fetch the complete documentation index at: https://archie.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Deploy from the IDE
After saving a function in the in-project IDE, click Deploy. Archie:- Lints and type-checks the handler
- Bundles dependencies
- Pushes to the target environment
- Routes traffic atomically (zero-downtime)
Deploy from local development
If you authored locally:- Push to your linked GitHub branch
- Open a PR (or merge to main, depending on your workflow)
- The Archie deploy workflow runs and deploys functions for the targeted environment
Environments and promotion
Functions deploy per-environment:- Preview — auto-deploys on every save
- Staging — manual deploy or PR-based
- Production — manual deploy with optional approval gates
Rollback
Each deploy creates a versioned record. Roll back from the function’s deploy history.FAQ
Can I deploy a single function without redeploying the whole app?
Can I deploy a single function without redeploying the whole app?
Yes — function deploys are independent of frontend and backend deploys.
What if my function depends on env vars that are not set in production?
What if my function depends on env vars that are not set in production?
The deploy fails. Configure env vars before deploying.
How do I deploy a queue-triggered function?
How do I deploy a queue-triggered function?
Same flow. The queue subscription is created or updated as part of the deploy.