Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.edgespark.dev/llms.txt

Use this file to discover all available pages before exploring further.

Today, new EdgeSpark projects start with one default production environment. That means edgespark deploy updates the live project environment directly.

​
Deploy

edgespark deploy
This builds your code and deploys it to your current project URL: 
✓ Schema synced
✓ Built in 1.4s
✓ Deployed

https://my-app.edgespark.app

​
Dry run

Validate your build without deploying: 
edgespark deploy --dry-run
A dry run builds your code and reports the routes found, but does not upload or deploy anything. Use this before live deploys or in CI to catch type errors and route mistakes early.

​
What a deploy does

When you run edgespark deploy:
  1. Schema sync — refreshes generated files in server/src/__generated__/
  2. Type check — verifies your code has no TypeScript errors
  3. Build — compiles your application to a single bundle
  4. Route analysis — scans and reports your routes grouped by auth convention
  5. Deploy — uploads your bundle and makes it live on the current default environment
See the deploy pipeline for a detailed walkthrough.

​
Current public environment model

Right now, EdgeSpark does not publicly expose a separate staging environment for newly created projects. So:
  • there is no public staging URL yet
  • there is no public deploy promote workflow to document yet
  • you should treat edgespark deploy as a deploy to the current live project environment
Staging support is coming soon. When it lands, the docs will add the isolated staging workflow and promotion model.

​
See also

The deploy pipeline

Detailed walkthrough of every step in edgespark deploy.

Environments

The current single-environment model and what is coming next for staging.
Last modified on April 7, 2026