From e1661518efdba5a0e3a0b2ee38240c126c2770d7 Mon Sep 17 00:00:00 2001 From: Lupancham <77426370+Lupancham@users.noreply.github.com> Date: Wed, 5 Nov 2025 12:15:04 -0500 Subject: [PATCH 1/7] Update docker.mdx --- content/docs/blueprint/migrations/docker.mdx | 27 ++++++++++++++++---- 1 file changed, 22 insertions(+), 5 deletions(-) diff --git a/content/docs/blueprint/migrations/docker.mdx b/content/docs/blueprint/migrations/docker.mdx index c17b3e5..6fa26a2 100644 --- a/content/docs/blueprint/migrations/docker.mdx +++ b/content/docs/blueprint/migrations/docker.mdx @@ -5,15 +5,32 @@ description: Guide for migrating from Pyrodactyl to Pyrodactyl (Blueprint) using ## Migrating from Pyrodactyl (Docker) -Always make sure you take a backup of your Pterodactyl database and other relevant data. +Always ensure that you make a backup of your Pyrodactyl database and any other relevant data. Provided below is how you can make a backup of your Panel Database. (Replace ``panel`` with the database name you use) + +``` +# If using MySQL +mysqldump -u root -p --opt panel > ./panel.sql + +# If using MariaDB +mariadb-dump -u root -p --opt panel > ./panel.sql +``` -If you already have Pyrodactyl running in Docker, simply update your panel image in your `docker-compose.yml` file: +If you already have Pyrodactyl running in Docker, update your panel image and add these volumes to your `docker-compose.yml` file: ```diff --image: ghcr.io/pyrohost/pyrodactyl:main -+image: ghcr.io/pyrodactyl-oss/blueprint:latest +panel: + -image: ghcr.io/pyrohost/pyrodactyl:main + +image: ghcr.io/pyrodactyl-oss/blueprint:latest + +volumes: + - '/srv/pterodactyl/var/:/app/var/' + - '/srv/pterodactyl/nginx/:/etc/nginx/http.d/' + - '/srv/pterodactyl/certs/:/etc/letsencrypt/' + - '/srv/pterodactyl/logs/:/app/storage/logs' + +- "/srv/pyrodactyl/extensions/:/blueprint_extensions" + +- "app:/app" ``` Switching back from Blueprint to Pyrodactyl is not supported. We do not provide any support for this and cant guarantee that it will work. If you care about your data, **make a backup** before switching. - \ No newline at end of file + From d994d1e7e528a773bf8248fb68378bb8c3b7fe08 Mon Sep 17 00:00:00 2001 From: Lupancham <77426370+Lupancham@users.noreply.github.com> Date: Wed, 5 Nov 2025 12:20:00 -0500 Subject: [PATCH 2/7] Update docker.mdx --- content/docs/blueprint/migrations/docker.mdx | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/content/docs/blueprint/migrations/docker.mdx b/content/docs/blueprint/migrations/docker.mdx index 6fa26a2..66dc6f1 100644 --- a/content/docs/blueprint/migrations/docker.mdx +++ b/content/docs/blueprint/migrations/docker.mdx @@ -23,12 +23,8 @@ panel: +image: ghcr.io/pyrodactyl-oss/blueprint:latest volumes: - - '/srv/pterodactyl/var/:/app/var/' - - '/srv/pterodactyl/nginx/:/etc/nginx/http.d/' - - '/srv/pterodactyl/certs/:/etc/letsencrypt/' - - '/srv/pterodactyl/logs/:/app/storage/logs' - +- "/srv/pyrodactyl/extensions/:/blueprint_extensions" - +- "app:/app" + + - "/srv/pyrodactyl/extensions/:/blueprint_extensions" + + - "app:/app" ``` From 72437587ab0425caaa3f4346c7903d325bfc0a81 Mon Sep 17 00:00:00 2001 From: Lupancham <77426370+Lupancham@users.noreply.github.com> Date: Wed, 5 Nov 2025 12:22:49 -0500 Subject: [PATCH 3/7] Update native-to-docker.mdx --- .../docs/pyrodactyl/migrations/native-to-docker.mdx | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/content/docs/pyrodactyl/migrations/native-to-docker.mdx b/content/docs/pyrodactyl/migrations/native-to-docker.mdx index 8dd4df5..3036848 100644 --- a/content/docs/pyrodactyl/migrations/native-to-docker.mdx +++ b/content/docs/pyrodactyl/migrations/native-to-docker.mdx @@ -51,6 +51,19 @@ description: Guide for migrating from native Pterodactyl installation to Pyrodac ``` 1. If your database is running on the same machine as your panel, set it to listen on the IP `172.17.0.1`, and change the `DB_HOST` environment variable to `172.17.0.1`. + + +Once you switch to Pyrodactyl, switching back to Pterodactyl is not supported and may cause errors. Provided below is how you can make a backup of your Panel Database if you need to switch back. (Replace ``panel`` with the database name you use) + +``` +# If using MySQL +mysqldump -u root -p --opt panel > ./panel.sql + +# If using MariaDB +mariadb-dump -u root -p --opt panel > ./panel.sql +``` + + 1. Rename `docker-compose.example.yml` to `docker-compose.yml` 1. Run the following command to start the panel: ```bash From 426074d4b78f3e47983daadcee29e759576b5efb Mon Sep 17 00:00:00 2001 From: Lupancham <77426370+Lupancham@users.noreply.github.com> Date: Wed, 5 Nov 2025 12:23:51 -0500 Subject: [PATCH 4/7] Update native-to-docker.mdx --- .../migrations/native-to-docker.mdx | 24 +++++++++---------- 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/content/docs/pyrodactyl/migrations/native-to-docker.mdx b/content/docs/pyrodactyl/migrations/native-to-docker.mdx index 3036848..cfdebb8 100644 --- a/content/docs/pyrodactyl/migrations/native-to-docker.mdx +++ b/content/docs/pyrodactyl/migrations/native-to-docker.mdx @@ -14,6 +14,18 @@ description: Guide for migrating from native Pterodactyl installation to Pyrodac - Avoid using Snap-based Docker installations on Ubuntu - Enable Docker auto-start on boot + +Once you switch to Pyrodactyl, switching back to Pterodactyl is not supported and may cause errors. Provided below is how you can make a backup of your Panel Database if you need to switch back. (Replace ``panel`` with the database name you use) + +``` +# If using MySQL +mysqldump -u root -p --opt panel > ./panel.sql + +# If using MariaDB +mariadb-dump -u root -p --opt panel > ./panel.sql +``` + + ### Pyrodactyl Installation 1. Create a new folder (e.g. `pyrodactyl-panel`) on your server in a safe location, and switch to it. @@ -52,18 +64,6 @@ description: Guide for migrating from native Pterodactyl installation to Pyrodac 1. If your database is running on the same machine as your panel, set it to listen on the IP `172.17.0.1`, and change the `DB_HOST` environment variable to `172.17.0.1`. - -Once you switch to Pyrodactyl, switching back to Pterodactyl is not supported and may cause errors. Provided below is how you can make a backup of your Panel Database if you need to switch back. (Replace ``panel`` with the database name you use) - -``` -# If using MySQL -mysqldump -u root -p --opt panel > ./panel.sql - -# If using MariaDB -mariadb-dump -u root -p --opt panel > ./panel.sql -``` - - 1. Rename `docker-compose.example.yml` to `docker-compose.yml` 1. Run the following command to start the panel: ```bash From c0b786be483d62474c308564ad7bd41406f01172 Mon Sep 17 00:00:00 2001 From: Lupancham <77426370+Lupancham@users.noreply.github.com> Date: Wed, 5 Nov 2025 12:25:20 -0500 Subject: [PATCH 5/7] Update native-to-docker.mdx --- .../docs/pyrodactyl/migrations/native-to-docker.mdx | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/content/docs/pyrodactyl/migrations/native-to-docker.mdx b/content/docs/pyrodactyl/migrations/native-to-docker.mdx index cfdebb8..1a70275 100644 --- a/content/docs/pyrodactyl/migrations/native-to-docker.mdx +++ b/content/docs/pyrodactyl/migrations/native-to-docker.mdx @@ -5,6 +5,18 @@ description: Guide for migrating from native Pterodactyl installation to Pyrodac ## Migrating from Pterodactyl (Native → Docker) + +Once you switch to Pyrodactyl, switching back to Pterodactyl is not supported and may cause errors as Pyrodactyl modifies the Pterodactyl Database Schema. Provided below is how you can make a backup of your Panel Database if you need to switch back. (Replace ``panel`` with the database name you use) + +``` +# If using MySQL +mysqldump -u root -p --opt panel > ./panel.sql + +# If using MariaDB +mariadb-dump -u root -p --opt panel > ./panel.sql +``` + + ### Prerequisites - Linux system with root access From d149864c6d3420267fee503a6ba288620cdb368b Mon Sep 17 00:00:00 2001 From: Lupancham <77426370+Lupancham@users.noreply.github.com> Date: Wed, 5 Nov 2025 12:26:36 -0500 Subject: [PATCH 6/7] Update native-to-native.mdx --- .../pyrodactyl/migrations/native-to-native.mdx | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/content/docs/pyrodactyl/migrations/native-to-native.mdx b/content/docs/pyrodactyl/migrations/native-to-native.mdx index 139181b..621eba6 100644 --- a/content/docs/pyrodactyl/migrations/native-to-native.mdx +++ b/content/docs/pyrodactyl/migrations/native-to-native.mdx @@ -5,10 +5,16 @@ description: Guide for migrating from native Pterodactyl installation to native ## Migrating from Pterodactyl (Native → Native) - - Before making any changes, back up your entire panel directory and database. - Pyrodactyl modifies the database schema, and rolling back to Pterodactyl may - result in data loss or instability. + +Once you switch to Pyrodactyl, switching back to Pterodactyl is not supported and may cause errors as Pyrodactyl modifies the Pterodactyl Database Schema. Provided below is how you can make a backup of your Panel Database if you need to switch back. It is also recommended that you make a backup of the Pterodactyl folder aswell if anything goes wrong during migration. (Replace ``panel`` with the database name you use) + +``` +# If using MySQL +mysqldump -u root -p --opt panel > ./panel.sql + +# If using MariaDB +mariadb-dump -u root -p --opt panel > ./panel.sql +``` ### Prerequisites From 748554f0f1901a9e9967ce11a2a5f5569cdb8eae Mon Sep 17 00:00:00 2001 From: Lupancham <77426370+Lupancham@users.noreply.github.com> Date: Wed, 5 Nov 2025 12:28:14 -0500 Subject: [PATCH 7/7] Update native-update.mdx --- content/docs/pyrodactyl/migrations/native-update.mdx | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/content/docs/pyrodactyl/migrations/native-update.mdx b/content/docs/pyrodactyl/migrations/native-update.mdx index 134968d..4442335 100644 --- a/content/docs/pyrodactyl/migrations/native-update.mdx +++ b/content/docs/pyrodactyl/migrations/native-update.mdx @@ -10,8 +10,15 @@ Newest release version: ![Pyrodactyl Latest Release](https://img.shields.io/github/v/release/pyrohost/pyrodactyl?style=for-the-badge) - Before proceeding with any updates, make sure to back up your database and - panel files. + Before proceeding with any updates, make sure to back up your database and panel files. Provided below is how you can make a backup of your Panel Database. (Replace ``panel`` with the database name you use) + +``` +# If using MySQL +mysqldump -u root -p --opt panel > ./panel.sql + +# If using MariaDB +mariadb-dump -u root -p --opt panel > ./panel.sql +``` ### Prerequisites