Comments
4 comments
-
I probably should have researched the Flyway Support site better before posting this, as it is recommended by Redgate not to do this for this very reason...
https://documentation.red-gate.com/flyway/learn-more-about-flyway/troubleshooting/projects-in-onedrive
-
Check if the files are syncing correctly between devices or if OneDrive is running in a "read-only" state for some reason. -
I’ve actually run into a similar issue when trying to use Microsoft OneDrive as a repository location. The core problem is that OneDrive syncs files in a way that can sometimes lock or restrict permissions when applications (like Flyway) try to write directly into the synced directory. That’s why you were able to initially create the project and folders, but later faced errors when Flyway attempted to save new changes.
A couple of things you can try:
- Check OneDrive Sync Settings – Ensure “Files On-Demand” is disabled. When enabled, OneDrive may store files in the cloud only and fetch them on demand, which often breaks repository-based tools.
-
Local Path Exclusion – Set up your repository in a standard local directory (e.g.,
C:\Repos\Project) and then use OneDrive Backup or Sync to mirror that folder to the cloud. This way, Flyway interacts with a normal file system while OneDrive handles syncing in the background. - Permissions – Right-click on the OneDrive repository folder and make sure your account has full read/write permissions. Occasionally, inherited permissions get messed up during sync.
- Alternative Sync – Some developers avoid putting repositories directly in OneDrive and instead rely on Git remote hosting (like GitHub, GitLab, or Bitbucket) for synchronization, while using OneDrive strictly for backup.
Others have reported that while OneDrive is fine for regular file storage, it’s not always reliable for active repositories due to conflicts and permission locks. If you’re frequently switching between two computers, Git remotes may be the more stable solution.
-
Thanks for sharing this setup. Installing a Flyway Desktop repository inside a OneDrive-synced folder can be convenient for backups, but it’s important to be careful with sync conflicts—especially when multiple machines or users are involved. Similar to installing applications like Roblox for PC, Flyway Desktop on a Windows PC works best when files are stored in a stable, locally managed location. For database migrations, using proper version control (such as Git) instead of relying solely on OneDrive syncing can help avoid issues like file locking, partial syncs, or unexpected conflicts.
Add comment
Please sign in to leave a comment.
I was just wondering if anybody else has attempted this, and if so did you have to resolve this issue?