Compare commits

..

No commits in common. "daf41efa4c4c95f5ba16f1500ad06a6f0518a043" and "cada9dd67c09f2d97a6207fe62b9c8b0d00aae40" have entirely different histories.

2 changed files with 0 additions and 22 deletions

View File

@ -4,20 +4,6 @@ All notable changes to this project will be documented in this file.
--- ---
## Unreleased
#### Links
- upstream: https://code.lindeas.com/lindeas/jilo-web/compare/v0.2.1...HEAD
- codeberg: https://codeberg.org/lindeas/jilo-web/compare/v0.2.1...HEAD
- github: https://github.com/lindeas/jilo-web/compare/v0.2.1...HEAD
- gitlab: https://gitlab.com/lindeas/jilo-web/-/compare/v0.2.1...HEAD
### Added
- Added Jilo Server check and notice on error
- Added status page
---
## 0.2.1 - 2024-10-17 ## 0.2.1 - 2024-10-17
#### Links #### Links

View File

@ -38,14 +38,6 @@ It's a multi-user web tool with user levels and access rights integrated into it
The current website you are looking at is running a Jilo Web instance. The current website you are looking at is running a Jilo Web instance.
<hr /><strong>"Jilo Server"</strong>
Jilo Server is a server component written in Go, meant to work alongside Jilo Web. It is responsible for all automated tasks - health checks, periodic retrieval of data from the remote Jilo Agents, etc.
It generally works on the same machine as the web interface Jilo Web and shares its database, although if needed it could be deployed on a separate machine.
Jilo Web checks for the Jilo Server availability and displays a warning if there is a problem with the server.
</div> </div>
</div> </div>