Deploy Pterodactyl Panel + MariaDB

Deploy and Host Pterodactyl Panel + MariaDB on Railway

Run the Pterodactyl Panel on Railway with private MariaDB, Redis, a Panel volume, and a first admin created on boot.

About Hosting Pterodactyl Panel + MariaDB

The template starts three services:

• panel: public Pterodactyl Panel, pinned to v1.15.1
• MariaDB: private MariaDB 11.8 with a volume at /var/lib/mysql
• Redis: private cache, session, and queue store

The Panel volume at /app/var keeps the generated APP_KEY. A missing volume would mint a new key on every deploy and make encrypted node tokens unreadable.

This template runs the Panel only. It does not run Wings or game servers. Connect Wings from machines that support Docker, ports, and game workloads.

Common Use Cases

• Pterodactyl Panel hosting
• Game-server admin dashboards
• External Wings node management

Dependencies for Pterodactyl Panel + MariaDB Hosting

The Panel needs MariaDB for application data, Redis for cache/session/queue, persistent Panel storage, and Wings nodes you run yourself.

Deployment Dependencies

• APP_URL: public Panel URL
• DB_*: private MariaDB connection
• REDIS_*: private Redis connection
• ADMIN_PASSWORD: first-admin password, same value as the MariaDB password

After Deploy

1. Open the Panel public URL.
2. Log in as admin@example.com.
3. Copy ADMIN_PASSWORD from the panel service variables.
4. Change that password.
5. Add Wings nodes on separate infrastructure.

Why Deploy Pterodactyl Panel + MariaDB on Railway

Railway hosts the Panel, MariaDB, and Redis so you do not have to wire private networking, volumes, or generated secrets by hand. Game servers still run on Wings, not on this stack.