Outcome
You understand when Manual, Automatic Export, Automatic Import, Full Automatic Sync, and Workflow mode are appropriate, and how to avoid cascading data loss.
Full Automatic Sync Safety
Use automatic import/export modes without creating loops or overwriting environment-specific data.
Video walkthrough
▶
Video walkthrough coming soon.
The YouTube embed will appear here.Risk level
High. Automatic write modes can surprise teams. Roll out gradually and monitor Activity.
Before you start
- Know which site is source and which is target.
- Use Git or backups before enabling automatic writes.
- Exclude environment-specific options and secrets.
Mode guide
| Constant | Type | Default | Description |
|---|---|---|---|
BRICKSSYNC_STORAGE_PATH | string | /uploads/bricks-sync | Directory for snapshot files. |
BRICKSSYNC_MODE | string | two-way | Sync direction. |
BRICKSSYNC_AUTO_EXPORT | bool | false | Export when Bricks saves. |
BRICKSSYNC_GIT | bool | false | Auto-commit snapshots. |
Safety checklist
- Start manual.
- Enable export-only first.
- Review JSON diffs.
- Add import automation only on staging.
- Use exclusions for environment-specific settings.
- Monitor Activity after every mode change.
Auto-export during import is guarded
Recent code prevents cascading data loss by avoiding auto-export during import operations, but automatic modes still deserve careful rollout.Screenshots
