Outcome
Conflicts are resolved intentionally instead of accidentally replacing target-site work.
Conflict Resolution in Practice
Choose skip, overwrite, merge, or prompt based on ownership and risk.
Video walkthrough
▶
Video walkthrough coming soon.
The YouTube embed will appear here.Risk level
High. Wrong conflict choice can replace production data. Prefer prompt when unsure.
Before you start
- Know whether source or target is authoritative.
- Run dry runs for any production import.
- Keep backups until verification is complete.
Strategy 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. |
Runbook
- Dry-run the import.
- Open pending conflicts in Config/Tools or the import UI.
- Compare source and target.
- Apply the chosen strategy.
- Import and verify Activity.
Screenshots
Prompt before overwrite
For pages, fields, global styles, and production templates, prompt/dry-run is safer than default overwrite.