Sadly, it seems that you’ll have to make the change again and again… that’s what I used to do back in May/June. Note that when compiling Pydio Cells from the source I could not upgrade it through the UI (it remains ‘stuck’ on version 0.1.0 or something); this is to be expected since FreeBSD is not supported by Pydio, and so the auto-update feature will not be able to download a FreeBSD binary… that seems logical, of course, but I was baffled the first time I managed to compile Cells. It won’t even be able to figure out if there is a new version… you’ll have to do all the downloading/compiling on your own — in my case, I used git to periodically get the latest code, patch it manually with the changes I suggested, and compile it from scratch again and again…
Note that the main issue here is that Pydio Cells ‘assumes’ that there is OS support of keyrings, which seems to be the case with Linux and macOS (and possibly Windows as well), although, of course, each case works differently. The package mentioned (github.com/zalando/go-keyring) is used by the Pydio developers to encapsulate keyring access in a transparent manner; sadly, though, FreeBSD doesn’t support keyrings at the OS level — @zalando, however, was clever enough to include an option for user-level keyrings, for those OSes that don’t have OS-level keyring support, and this used to work well under FreeBSD 16.04; the only change that was required was to force Cells to allow that feature of the go-keyring package to be used (by default, Cells’ code will fail, as you have noticed). Note that technically the Pydio dev team could make that change ‘forever’ (because it won’t hurt any other OS with built-in keyring support) but I can very well understand that they won’t change their well-tested code with an ‘unknown feature’…
Unfortunately, I have not been able to get the latest version of Pydio Cells compiled under FreeBSD, either, but to be honest, I haven’t been trying hard enough 