ServPulse: Difference between revisions
From Nasqueron Agora
No edit summary |
(Description) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
'''ServPulse''' is a status | '''ServPulse''' is an open-source status-page platform for publishing the status of services, components, and infrastructure. Its goal is to make it easy to communicate incidents, maintenance, and uptime metrics in a transparent way. | ||
ServPulse is designed to be self-hostable, simple to deploy, and extensible. It provides a foundation for teams and communities to manage status pages, integrate with monitoring tools, and notify users automatically. | |||
The project is community-driven: contributions to the code, documentation, themes, integrations, or translations are all welcome. ServPulse aims to remain open, reliable, and adaptable to different environments, while keeping the setup and use straightforward. | |||
== Technology stack == | == Technology stack == | ||
| Line 13: | Line 17: | ||
== Team == | == Team == | ||
* [https://devcentral.nasqueron.org/p/ | * [https://devcentral.nasqueron.org/p/ieli/ Eli] (lead developer) | ||
* [[User:Dereckson|Dereckson]] (technical advisory) | * [[User:Dereckson|Dereckson]] (technical advisory) | ||
| Line 22: | Line 26: | ||
== Activities == | == Activities == | ||
; Analysis | |||
* [[/Note of Intent]] | |||
* [[/Other existing solutions]] | |||
* [[/Development guide]] | * [[/Development guide]] | ||
* [[/Project identity]]: why ServPulse name | * [[/Project identity]]: why ServPulse name | ||
Latest revision as of 18:05, 25 October 2025
ServPulse is an open-source status-page platform for publishing the status of services, components, and infrastructure. Its goal is to make it easy to communicate incidents, maintenance, and uptime metrics in a transparent way.
ServPulse is designed to be self-hostable, simple to deploy, and extensible. It provides a foundation for teams and communities to manage status pages, integrate with monitoring tools, and notify users automatically.
The project is community-driven: contributions to the code, documentation, themes, integrations, or translations are all welcome. ServPulse aims to remain open, reliable, and adaptable to different environments, while keeping the setup and use straightforward.
Technology stack
- Back-end
- Express.js service
- API documented according OpenAPI specification
- PostgreSQL database
Team
Thanks for help to map stories:
- DorianWinty
- Fauve
Activities
- Analysis
- /Note of Intent
- /Other existing solutions
- /Development guide
- /Project identity: why ServPulse name
- /Domain: names used in the project
- /User stories
