Releases: aternosorg/mclogs
v2.2.0
New
- Apply filters in client Javascript
- Added API endpoint to get current filters
Fixes
- Improved transitions
- Fixed full width setting on header
- Fixed full width setting on mobile
- Fixed footer padding
- Fixed display issues in Firefox by using table display for Firefox
- Removed old logo
- Replaced favicon.ico with the new logo
v2.1.0
New
- Read protocol from proxy headers
- Added trusted proxies config
- Improved asset loading + cache busting
- Sync settings across open browser tabs
- Added an "Overflow" setting to enable zooming in and out on mobile devices
Fixes
- Only show delete button when a valid token exists
- Fixed log deletion
- Fixed errors output in page description
- Set the body to full width on mobile devices for better usability
- Reduced the font size on mobile devices
- Improved performance by eliminating hover states on log lines
- Resolved the issue of Metadata/Detected data not wrapping properly on mobile devices
- Restructured the DOM and removed outdated containers
v2.0.0
7708afc
matthi4s
Matthias Neid
We've completely rewritten mclo.gs from the ground up to bring the code, the tooling and design up to modern standards.
Highlights
- New modern design
- Support for Minecraft & Hytale
- Metadata API
- Source string
- Log deletion
- Full self-hosting support
Metadata API
You can now add metadata when sending logs through the API. Metadata entries are key/value pairs with an optional display label to add additional context to your logs, e.g. software versions, server IDs etc. They are visible by default but can be hidden to be only available through the API. Read the full API documentation here: https://api.mclo.gs
Source string
API users can now identify the source of their logs by sending a source string alongside the log content. This source string is displayed at the bottom of each log page and is retrievable in the API. Read the full API documentation here: https://api.mclo.gs
Log deletion
When creating a new log using the API, a token is returned that can be used to delete the log later if necessary. Read the full API documentation here: https://api.mclo.gs
Logs created via the frontend (https://mclo.gs) automatically store the token in a cookie. Those logs can then be deleted directly on the log page.
Self-hosting
While self-hosting mclo.gs was always possible, it was never officially supported and required direct code changes. The new version is released as a deployment ready docker image with extensive configuration support. Check the README for more information.
Backwards compatibility
The old version of mclo.gs supported multiple data storage methods (mongodb, redis, filesystem). The support for redis and the filesystem was removed in the new version to simplify development. Logs already stored in mongodb are fully compatible with the new version.
Simplifying the storage also removes the need to encode the storage backend in the ID. The new version still checks for IDs in the old format (without the first character) if necessary to maintain backwards compatibility with old data.