Ugrás a fő tartalomhoz
Deploy all your project resources to Base44 in a single command. This includes entities, functions, actors, connectors, agents, agent skills, auth config, the build code for your frontend, and the app’s visibility level when set in config.jsonc. The command provides a summary of what will be deployed and asks for confirmation before proceeding.
The confirmation summary lists resource counts, but does not call out which resources will be deleted. Review the sync behavior section below before running deploy on a project where you may have removed local entities, agents, or agent skills.
If any connectors require OAuth authorization, the deploy command prompts you to authorize them in your browser, similar to running connectors push. If a connector fails to sync, the deploy fails after the rest of your resources and your site are deployed. You can also deploy resources individually using entities push, functions deploy, actors deploy, connectors push, auth push, and site deploy. If your project has a frontend, pass --build to compile it before deploying, or run base44 build separately first. In an interactive terminal, the command asks whether to build if you pass neither flag. Without an interactive terminal, such as in CI or an AI agent environment, the command requires --yes. It also skips the build unless you pass --build. It then deploys whatever build is already in your output directory, or the site deploy fails if there’s none.

Usage

Flags

Example

Build the site and deploy without prompts, for example from a script or an AI agent:

Output

When the deploy finishes, the command prints a link to your app’s dashboard. If your project has a site, it also prints the live app URL:

Sync behavior

The deploy command creates and updates all resource types, but handles deletions differently for functions, actors, and connectors than for entities, agents, and agent skills.

Entities, agents, and agent skills

Entities, agents, and agent skills are fully synced, the same way as entities push, agents push, and agent-skills push. Remote resources not found locally are removed:
Removing an entity removes its schema from Base44. Existing data is not deleted, but the entity will no longer be accessible through the SDK.If your project has no local agents, or no local agent skills, that resource type is left untouched rather than deleted. Otherwise, any remote agent or agent skill missing from your local files is removed, even though the confirmation summary does not list it separately.

Functions, actors, and connectors

Functions, actors, and connectors are deployed but not pruned. Remote functions, actors, and connectors not found locally are left unchanged. To remove remote functions that are no longer in your project, use functions deploy --force. To remove remote actors, use actors delete. To remove remote connectors, use connectors push --force.

See also

  • build: Build the site without deploying
  • Entities: Learn about database schema configuration
  • Connectors: Set up OAuth connections to third-party services
  • About Agents: Configure AI agents for your app
  • Agent Skills: Define reusable instruction sets for your agents
  • Backend Functions: Create serverless API endpoints
  • functions deploy: Deploy functions individually with selective deploy and pruning options