One big DB will be a single point of failure. You will not benefit from much more speed, the only thing which is "easier" is backup. I use different DBs for different stacks. If one hangs up or messed up completly, it won't affect others
I setup Floccus on Vivaldi and tried it now with Firefox... Works fineI use it with Nextcloud but as WebDAV setup. Be careful with the paths! If you use a subfolder don't add / at the beginning.
Yesterday my post was stuck too. I wuickly used edit function and then it was properly federated ☺️Just edit, save it, done
The permissions are not set right with the cap drop abilities. Comment out cap drop lines fir the first start. The files are created now. Then you can undo outcommenting and restart again
There are 2 lines "cap drop"You need to comment them out for the first startThe files are created, then remove outcommenting and restart againYou can use my docker-compose.ymlStart it and the stop it. Remove then the # on line 30 and 31. Start up again ☺️
In MinIO you can selfhost the server. I named a bucket and user alex and I am pretty sure someone had the same idea 😁Bucket and usernames don't need to be globally unique in MinIO. I tried the policy and it worked pretty good ☺️
Yes each user can have a private bucket and only this one. I am not this much into policies and I was lucky to get this template. Maybe it gives you an idea how to modify it for your needs. If you found a solution, please share ☺️
One big DB will be a single point of failure. You will not benefit from much more speed, the only thing which is "easier" is backup.
I use different DBs for different stacks. If one hangs up or messed up completly, it won't affect others