9ff713c537
Using index is bad practice: https://react.dev/learn/rendering-lists#rules-of-keys We don't recalculate the overflow state once the message is overflown. When using the index as key, then when a new message is added at the top of the array at index 0. The overflow state from the previous message at index 0 is kept. The overflow state shouldn't be reused. |
||
|---|---|---|
| .github | ||
| api | ||
| auth | ||
| config | ||
| database | ||
| docker | ||
| docs | ||
| error | ||
| mode | ||
| model | ||
| plugin | ||
| router | ||
| runner | ||
| test | ||
| ui | ||
| .dockerignore | ||
| .editorconfig | ||
| .gitignore | ||
| .golangci.yml | ||
| CODEOWNERS | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| GO_VERSION | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| SECURITY.md | ||
| app.go | ||
| config.example.yml | ||
| go.mod | ||
| go.sum | ||
| renovate.json | ||
| ui.png | ||
README.md
gotify/server
Intro
We wanted a simple server for sending and receiving messages (in real time per WebSocket). For this, not many open source projects existed and most of the existing ones were abandoned. Also, a requirement was that it can be self-hosted. We know there are many free and commercial push services out there.
Features
- send messages via REST-API
- receive messages via WebSocket
- manage users, clients and applications
- Plugins
- Web-UI -> ./ui
- CLI for sending messages -> gotify/cli
- Android-App -> gotify/android
(Google Play and the Google Play logo are trademarks of Google LLC.)
Install ᛫ Configuration ᛫ REST-API ᛫ Setup Dev Environment
Contributing
We welcome all kinds of contribution, including bug reports, feature requests, documentation improvements, UI refinements, etc. Check out CONTRIBUTING.md for guidelines.
Versioning
We use SemVer for versioning. For the versions available, see the tags on this repository.
License
This project is licensed under the MIT License - see the LICENSE file for details