
Local storage with read-only shared database
Closed this issue ยท 2 comments
Description
Hi!
I asked ChatGPT about a solution for synchronizing the permissions/groups on every server, but keeping the database read-only in a way that the owners of the subservers can add extra permissions, but it should be stored only locally, not in the shared database.
It recommended to modify a config value that doesn't exist, and I thought that a feature like this would be a great idea.

Proposed Behaviour
- Configure a read-only MySQL database.
- Synchronize every permissions/groups over all subservers that I can manage on the bungeecord.
- Keep every changes on the subservers locally, so it won't affect the whole server. (Server owners can't give themselves admin permissions globally or to other subservers.)
Extra Details
Add a read-only-mode
to the configuration, and some kind of local-storage-method
. LP will read all permissions and groups from the database while keeping track of local changes in the local files.
You can already achieve this behaviour with Argument-based command permissions. This permissions architecture would run into a lot of conflicts and no easy way to resolve them.
If you want to do this more simply, just configure some global perms on one instance and use lp export/import
commands to import them to all the other servers. Then, keep the subservers disconnected from the database and they'll operate independently of each other.
This has nothing to do with what I would like to have.
I don't want manually export/import on every server after every change I make.
An example behavior:
- Check permissions first on local database. (read-write, stored on the server, in the plugin's folder)
- If no match, check in the shared read-only database.