We are a group of students passionate about software engineering, building robust web platforms, and exploring modern DevOps architectures. This organization serves as the home for our collaborative projects.
Turning effort into excellence.
Status: ✅ Active / Stable
Deployed on medals.jannekeipert.de
"Medals" is a comprehensive web platform designed to revolutionize performance tracking for athletes and coaches. It provides a centralized, secure, and user-friendly solution to record, analyze, and visualize performance metrics.
- For Athletes: A personal digital trophy case to log achievements and track progress.
- For Coaches: A command center to monitor team performance and manage administrative overhead.
- Tech Highlights: Role-based security, data visualization, and CSV bulk imports.
The system is built on a robust Java Spring Boot backend and a responsive React frontend, containerized with Docker.
| Component | Description | Repository |
|---|---|---|
| Backend | Java Spring Boot REST API handling auth, logic, and data structures. | Medals-Backend |
| Frontend | React + TypeScript SPA providing the interactive dashboard. | Medals-Frontend |
| Deployment | Docker Compose & Nginx configuration for containerized deployment. | Medals-Deployment |
The Digital Caretaker for Game Servers.
Status: 🚧 In Development
Cosy is an open-source platform for the orchestration and management of game servers (like Minecraft, Valheim, or CS:GO). Unlike typical administrative dashboards, Cosy features a unique "village" aesthetic where servers are represented as buildings in a pixel-art world.
- Cost Efficiency: Optimized for performance on single-host systems (root servers / VPS).
- Isolation: Every game server runs in its own Docker container.
- Advanced Observability: Uses Loki for log aggregation (allowing live console streaming via WebSockets) and InfluxDB for performance metrics.
- Docker-based runtime: Game servers are managed through the Docker engine — that is the only container runtime Cosy drives. Cosy itself can be deployed on Kubernetes; that is a deployment choice, not a second runtime engine.
Cosy uses a Java control plane surrounded by focused services for the template catalog, documentation and game integrations.
| Component | Description | Repository |
|---|---|---|
| Release | The official Cost Optimized Server Yard download repo — also where issues for every Cosy repository are tracked. | Cosy |
| Backend | Java Spring Boot application acting as the central control center and log router. | Cosy-Backend |
| Frontend | React + TypeScript (Bun) interface rendering the "Village" UI. | Cosy-Frontend |
| Template Service | Go (Gin) microservice serving the template and game catalog to the backend. | Cosy-Template-Service |
| Templates | Official and community-maintained game/server template definitions (schema-validated YAML) consumed by the template service. | Cosy-Templates |
| Minecraft Mod | Server-side Fabric mod pushing live Minecraft metrics (players, TPS) back to the backend. | Cosy-Minecraft-Integration-Mod |
| Documentation | The official Cosy documentation site (cosy-hosting.net). | Cosy-Docs |
| Game API | Maintenance mode. Rust microservice wrapping the SteamGridDB API. Game data has moved to the template service (/v3/games); kept for older backends. |
Cosy-Game-Service |
| Deployment | Kubernetes manifests for the maintainers' internal test environments. | Cosy-Internal-Deployment |
Across our projects, we utilize a modern and diverse technology stack:
Languages
Frameworks & Libraries
DevOps & Infrastructure
Data & Observability
Feel free to explore our repositories. If you have questions or want to contribute, open an issue in the respective repository!
This is the special .github repository for the Magenta-Mause organization. It holds two kinds of content:
- The organization profile page —
profile/README.md, which renders on the organization's public profile. - Org-wide GitHub templates and community health files — default issue/PR templates and community documents that GitHub automatically applies to every repository in the organization that does not provide its own copy.
| File | Purpose |
|---|---|
.github/ISSUE_TEMPLATE/bug_report.md |
Default bug report issue template |
.github/ISSUE_TEMPLATE/feature_request.md |
Default feature request issue template |
.github/ISSUE_TEMPLATE/config.yml |
Issue template chooser config (contact links) |
.github/PULL_REQUEST_TEMPLATE.md |
Default pull request template |
CODE_OF_CONDUCT.md |
Contributor Covenant code of conduct |
SECURITY.md |
How to report security vulnerabilities |
CONTRIBUTING.md |
How to file issues and submit PRs — added separately in #3 |
Note: Issues for all Cosy repositories are tracked centrally in Magenta-Mause/Cosy.
A default community health file only applies to a repository when that repository does not define its own equivalent. To override an org-wide default, add the corresponding file to the individual repository (in its root, its .github/ folder, or its docs/ folder). GitHub always prefers a repository's own file over the organization default. This lets any repo tailor a template or policy while every other repo continues to inherit the shared defaults from here.