
Modifying the same file from two different devices at the same time will result in conflicts. stfolder in your sync directory seems to fix this. stfolder directory on my phone tends to be be deleted on restart causing an error. Once both devices configurations have been saved, I placed my kdb file in the Folder Path on my Fedora installation, and watched it synced to the opposite device within short order. Click the Sharing tab, and add a ✔ to your Android device name. Fill in Folder Label, Folder ID, and Folder Path, where Folder ID is the same as the 🔑 Folder ID on Android. Under the Folders section, select Add Folder. Tap to enable the slider for your Fedora device name. Fill in the 🏷️ Folder Label, 🔑 Folder ID, and 📁 Directory. From the main screen click on the Folders tab, then on the + in the top right. Input the Android Device ID and add a Name, then click Save.
Click the Add Remote Device button under the Remote Devices heading. Input the Fedora system's Device ID and add a Name, tap ✔ to save. From the main screen click on the Devices tab, then on the + in the top right. Click Actions, then Show ID, record the ID. Click on the ≡ and click Show Device ID record the ID. Install via the Google Play Store, link available here. Uploads or downloads directly to remote devices. Connects directly to devices via a relay. Monitors folders registered to Syncthing. I found Syncthing while searching for Nextcloud/alternatives and initially dismissed it, but came back to it after dissatisfaction with NextCloud/alternatives. I dismissed this because it was too much work from a security/maintenance standpoint, and would cost money to deploy. I considered setting up my own NextCloud (or similar) service. I dismissed this pretty quickly as there were too many logistical dependencies, and I couldn't find a way to make it work with a locked Android device. I thought about a cron based rsync solution. If I was ok with that I might as well have stayed with Firefox Lockwise. I dismissed this, because it was a centralized service out of my control. A quick online search recommends using a service like Dropbox, or Google Drive. Wholly self owned solution to sync my KeePass db file between multiple machines.
It also means that I had to find a way of syncing that db between devices. KeePass tends to be the name you hear, and so I decided on that. When it comes to password security and open source. That being said, I wanted a solution that I owned, where my passwords are only ever stored on my devices. Before now, I had been using Firefox Lockwise, which is an amazing free service, by a similarly amazing company dedicated to OSS. I have wanted to become more secure with how I have handled my password management for a while now.