Background operation
Synchronization runs in the background with progress and cancellation: large uploads do not block the interface.
DockStudio · Sync module
Repositories and clouds — like a local drive
The module connects the application to external services: GitHub, GitLab and other repositories, as well as file storage — Yandex Disk, Google Drive, S3 and network folders. Files and repositories become data sources just like the local disk.
Why
Data lives in many places — work happens in one
Working data rarely lives in one place: source code in a repository, documents in the cloud, archives on a network drive. This usually means copying back and forth by hand — with inevitable version confusion. The synchronization module connects external services directly to the application: you see the repository and the cloud folder in the same tree as local files, work with them offline, and changes go back once a connection is available.
What you can connect
Code repositories
GitHubGitLabGiteaBitbucketAzure DevOpsSelf-hosted Git server
File storage
Yandex DiskGoogle DriveOneDriveNextcloudS3-compatibleWebDAVSMB / network foldersFTP / SFTP
The list is open-ended: connecting a new service means an adapter, not reworking the app.
Code repositories
Link a repository to an application project: history, branches, changes and issues are available from the interface, without switching to a separate client.
GitHubGitLabGiteaBitbucketAzure DevOpsSelf-hosted Git server
01
Cloning, branches, commits and merges
02
Diff view and file history
03
Pull requests and code review in a panel
04
Tasks and issues next to the code
05
CI build statuses per branch
06
Token or OAuth authorization
File storage
Cloud and network storage connect as file sources: project folders sync both ways with version and conflict control.
Yandex DiskGoogle DriveOneDriveNextcloudS3-compatibleWebDAVSMB / network foldersFTP / SFTP
01
Two-way folder synchronization
02
Selective sync by folder and file type
03
Offline cache and resume after interruption
04
File versions and conflict resolution
05
Multiple accounts connected at once
06
Direct links to files inside the application
Mechanics
How it works in the app
Sync is part of the platform, not a separate utility on the side. Application modules access external storage through the same interface as the local drive.
Queue and resume
An interrupted transfer resumes where it stopped; deferred operations queue up until a connection is available.
Operation log
What was synchronized and when, who initiated it, which files were skipped and why.
Conflict resolution
If a file was changed on both sides, the system shows both versions and lets you choose one or keep both.
Unified API for modules
Application modules work with external storage through the same interface as with the local disk.
Access control
A whitelist of allowed services, a ban on uploading certain data categories, permissions for connecting accounts.
Security
External services — only the permitted ones
The administrator defines the list of available services: in an air-gapped environment you can keep only internal ones — a self-hosted Git server, S3 storage and network folders — with external clouds disabled entirely. Access tokens are kept in the platform's secure storage and never end up in settings files.
The module is included in the Business and Enterprise editions; Community supports only the local disk and a self-hosted Git server.
In an air-gapped environment
- Your own Git server instead of external hosting
- S3 storage and network folders inside the perimeter
- External clouds fully disabled by policy
- A log of all operations with external sources
Need a service that’s not on the list?
Connecting a new storage or hosting service means an adapter to a ready-made interface. Tell us what you work with and we’ll estimate the timeline.