Dropbox Integration
Dropbox integration gives you another browser-first cloud storage option for DBModeler projects.
How Dropbox support works
Section titled “How Dropbox support works”DBModeler uses an OAuth 2.0 PKCE flow for authorization, then talks to Dropbox metadata and content endpoints to manage project files.
This keeps the workflow aligned with the rest of the product: the editor runs locally in the browser, and the provider stores the remote project artifact.
What Dropbox is good for
Section titled “What Dropbox is good for”Use Dropbox when you want:
- a non-Git remote copy of the project
- sync support across sessions and machines
- conflict handling around provider-backed project files
Conflict handling
Section titled “Conflict handling”DBModeler normalizes Dropbox file metadata into the same broader sync engine used by the other providers.
That means Dropbox participates in:
- change detection
- merge conflict workflows
- remote file hydration for cloud-backed project stubs
Caveats
Section titled “Caveats”- Dropbox support depends on the runtime client configuration.
- Access token lifetime is shorter than refresh-token-backed persistence, so refresh handling matters in longer sessions.
- The integration manages the DBModeler app-folder style workflow, not arbitrary Dropbox content management.
Next: Secret Manager