You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 3, 2024. It is now read-only.
This way PEX is still enabled and can provide at least some form of permissions resolution. What needs to be decided is what to do when the fallback backend is used:
Lock down the server and grant no permissions to anybody
Kick everyone on join
Send a message to anyone who joins giving information about the error (while taking one of the above actions)
The text was updated successfully, but these errors were encountered:
Pex can use two different data stores at the same time yet e.g. For migration of permissions storage.
Wouldn't it be nice to have a configuration switch to enable fallback from database to file based data store if the DB connection breaks. This would need to have a valid and mostly up to date replication of the permissions.yml extracted from the pex DB schema in a regular base or another external tool would be needed to realize those extraction via cronjob for example.
If this seems to be too complex is there a chance to get native MySQL reconnection within pex realized ?
This way PEX is still enabled and can provide at least some form of permissions resolution. What needs to be decided is what to do when the fallback backend is used:
The text was updated successfully, but these errors were encountered: