Yes, we have experience and advice: Don't do it!

It depends somewhat on what you wish to do.

1 - OS filesystems are reliable, networks are not.

This means that any SQLite file or multiple files will work correctly between multiple processes on the same operating system since the operating system will both respect file-locks and correctly report the locked status of a file on an OS-local device. Network file systems lie about this constantly and cannot be trusted.

2 - The main problem with not knowing or respecting the locked status of a file exists in WRITING data, reading is less sensitive to it in especially WAL mode.

So it really depends on what you want to do. Possible scenarios are:

• Have 1 OS write the DB and others are all just consumers (readers) of data - This should work fine with WAL mode and some tweaked settings.
• Have 1 OS create a DB file and send/push it to the other OSes that then consume the data - no problems here either.
• Have multiple OSes both read and write to the same file - This can never work, don't do it.

If the last scenario is really what you need, there are several options out there that run on top of sqlite to provide the sort of functionality. If you wish to keep many SQLite DB files in sync all the time - BedrockDB is the best option in my opinion, or if you fancy a more client-server approach with possibly user access control, there's sqlitening, Valentina DB (and others that can be googled) or you know, Postgres or MariaDB...