Ramses Server Changelog
Starting with this version, the Ramses Server is compatible only with versions of MySQL more recent than 8.0, though it can still use SQLite too.
- New syncing methods which are slower but more reliable, especially with big sets of data.
- Improved performance with big sets of data.
- When using SQLite, ‘VACUUM’ is run at regular intervals to optimize the size of the file and fix potential issues with failed queries.
- Refuse client connexions if they’re using the wrong version.
- Accepts requests with missing ‘Content-Type’ header. Assumes it’s JSON by default.
- We now provide tested Docker configurations to easily install and run Ramses Docker containers.
- Each instance of a Ramses Server now had a unique universal identifier (UUID) to make sure a client won’t connect to a wrong server by mistake.
- Added new server-side logs.
- The login requests now returns details (data) about the connected user (if login is successful).
- Ability to deactivate the session timeout.
- Fixed the user table in case a (removed) username already exists when creating a new user.
- Fixed installation issues when using SQLite.
- Added (debug) logs to the replies which can be shown by clients.
- Fixed issues when table prefixes start with a number.
- Fixed connection issues when the URL ends with a /
- Ignore some sync errors when not in Dev mode
- Changed and simplified data exchange.
- Added step general settings
- The Rubika Flavor is merged into the official add-on.
- Added update command
- Added publish settings
- Added import and update settings