We have a number of people in our church involved in services each week — music leaders, musicians, pastor, projector operators — who need to use OpenLP, and who need to make sure that they are all working with the same version of the song database, images and so forth. To make sure that the song database is correct and consistent we don't have everyone making changes, there is one person responsible for editing songs.
To keep this under control, yet have an easy and transparent way to then get updates out to all persons we looked at and tried Dropbox (have to pay for read-only shared access) and Google Drive (messes up the write permissions on the SQLite DB which makes OpenLP crash). The other problem with both of these services, particularly if you host the song database in 'the cloud', is they have no concurrency (multi-user) functionality to allow multiple working on files.
The method I used in the end is a Git
repository. I made a Git server (on a FreeBSD virtual machine), one could also use a free account at Github if you didn't mind your OpenLP setup/data being completely open to the Internet.
With a script now I have Windows, Mac & Linux users pulling down updates from the Git server so they are all fully in-step with edits to the song database. As some of the OpenLP folders & files are specific to users/machines we have a selective replication of folders/files in our Git setup.
As I mentioned our setup is now working, just curious if anyone else has done something similar?