Deploy all your project resources to Base44 in a single command. This includes entities, functions, connectors, auth config, and the build code for your frontend. The command provides a summary of what will be deployed and asks for confirmation before proceeding.
If any connectors require OAuth authorization, the deploy command will prompt you to authorize them in your browser, similar to running connectors push.
You can also deploy resources individually using entities push, functions deploy, connectors push, auth push, and site deploy.
Before running this command, ensure that your built frontend files are in the directory specified by site.outputDirectory in your config.jsonc file.
Usage
Flags
| Flag | Description |
|---|
-y, --yes | Skip the confirmation prompt |
Sync behavior
The deploy command creates and updates all resource types, but handles deletions differently for functions than for entities and connectors.
Entities and connectors
Entities and connectors are fully synced. Remote resources not found locally are removed:
| Local state | Remote state | Result |
|---|
| Resource exists | Resource exists | Remote resource is updated |
| Resource exists | Resource missing | New resource is created |
| Resource missing | Resource exists | Remote resource is 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.Removing a connector removes the OAuth connection from Base44. Functions that use the connector will fail until it’s reconnected.
Functions
Functions are deployed but not pruned. Remote functions not found locally are left unchanged. To remove remote functions that are no longer in your project, use functions deploy --force.
See also
