From adf2de1a4c1ccd91a3c126dbee0315ef92ee4bd6 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Thu, 2 Apr 2026 15:57:38 +0000 Subject: [PATCH 1/2] Initial plan From d5a55085cd1e06c7519c4e08fae143c3c57a8456 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Thu, 2 Apr 2026 16:22:59 +0000 Subject: [PATCH 2/2] Build README.md with full project description, setup guide, and architecture overview Agent-Logs-Url: https://github.com/Alleria-PL/Community-Modpack-Manager/sessions/69635446-704c-4eac-9581-99ae2a8f36e4 Co-authored-by: mrfroncu <23080746+mrfroncu@users.noreply.github.com> --- README.md | 76 ++++++++++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 75 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 90054ca..51de55d 100644 --- a/README.md +++ b/README.md @@ -1,2 +1,76 @@ # Community-Modpack-Manager -I needed simple solution that could host server and modpack client but give someone the tools to manage it without giving him root access. + +A simple, self-hosted solution for managing a Minecraft modpack server and its client distribution — without granting root or administrator access to your team members. + +## Overview + +Community-Modpack-Manager was built to solve a common problem: you want to let someone on your team update and manage a Minecraft modpack server and its corresponding client pack, but you don't want to give them full server access. This project ties together three proven tools to create a secure, easy-to-use management workflow: + +- **[Technic Launcher / Solder](https://www.technicpack.net/)** — hosts and distributes the modpack client to players. +- **[Pterodactyl Panel](https://pterodactyl.io/)** — provides a web-based game server management UI so administrators can start, stop, and update the server without SSH or root access. +- **[Cloudflare Zero Trust](https://www.cloudflare.com/zero-trust/)** — secures access to the management interfaces, so only authorized users can reach the admin tools, without exposing ports directly to the internet. + +## Features + +- Host and update a Minecraft modpack server through the Pterodactyl panel. +- Distribute the matching client modpack to players via Technic Launcher. +- Delegate day-to-day server management (restarts, config updates, mod updates) to trusted team members — no root or SSH credentials needed. +- All management UIs are protected behind Cloudflare Zero Trust; access is granted by identity, not by network location. + +## Architecture + +``` +Players + └─► Technic Launcher ──────────────────────────────► Modpack files (hosted) + │ +Admins / Moderators │ + └─► Cloudflare Zero Trust (identity check) │ + └─► Pterodactyl Panel ──► Game Server (Minecraft) ┘ +``` + +## Prerequisites + +| Tool | Purpose | +|------|---------| +| [Pterodactyl Panel](https://pterodactyl.io/panel/1.0/getting_started.html) | Game server management UI | +| [Technic Solder](https://docs.technicpack.net/solder/) (or static file host) | Modpack client distribution | +| [Cloudflare Zero Trust](https://developers.cloudflare.com/cloudflare-one/) | Access control / tunneling | +| A Linux server | Hosting everything above | + +## Setup + +### 1. Pterodactyl Panel + +1. Follow the [official Pterodactyl installation guide](https://pterodactyl.io/panel/1.0/getting_started.html) to install the panel and a Wings daemon on your server. +2. Create a new server in the panel using a Minecraft egg that matches your modpack's Forge/Fabric version. +3. Upload your modpack server files through the panel's file manager. +4. Create a panel user account for each team member who needs to manage the server — assign them only the permissions they need (no admin role required for day-to-day tasks). + +### 2. Technic Launcher / Solder + +1. Set up [Technic Solder](https://docs.technicpack.net/solder/) or use a static web server to host your modpack ZIP files. +2. Create a modpack entry on the [Technic Platform](https://www.technicpack.net/) pointing to your Solder or direct-download URL. +3. Keep the client-side modpack in sync with the server-side mods so players always run the correct version. + +### 3. Cloudflare Zero Trust + +1. Add your domain to Cloudflare. +2. Create a [Cloudflare Tunnel](https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/) that forwards traffic to your Pterodactyl Panel (and optionally your Solder instance). +3. Configure an **Access Application** in the Zero Trust dashboard to require authentication (e.g., email OTP, GitHub, or Google SSO) before the panel is reachable. +4. Add team members to the appropriate Access policies — they log in through Cloudflare and reach the Pterodactyl panel without needing VPN or direct server access. + +## Usage + +- **Players** install the modpack through Technic Launcher using the pack URL and play normally. +- **Server managers** log in at the Pterodactyl panel URL (protected by Cloudflare Zero Trust) to restart the server, update configs, or swap mods. +- **Modpack maintainers** upload updated mod ZIPs to the Solder/static host and bump the pack version; Technic Launcher automatically prompts players to update. + +## Security Notes + +- No team member ever needs SSH keys or root credentials for routine management tasks. +- All administrative traffic passes through Cloudflare's network; the panel port is never open directly on the server's firewall. +- Revoke access instantly by removing a user from the Cloudflare Zero Trust policy — no password resets or key rotation needed. + +## License + +This project is provided as-is. Feel free to adapt it to your own community's needs.