Skip to content

update pelican.md, pterodactyl.md #31

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
0x7d8 merged 1 commit into from
Jul 9, 2026
Merged

update pelican.md, pterodactyl.md #31

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion web/docs/additional/migrations/pelican.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,4 +23,4 @@ A normal install on a Linux box, Pelican running directly on the host. Head to t
Pelican running inside Docker containers, with a `docker-compose.yml` somewhere. Head to the [Dockerized](./pelican/docker.md) guide.
::::

If you're not sure which you have, check what's actually running. Run `docker compose ps` in your Pelican directory: if it lists an active panel/web container, you're Dockerized. If the panel is served by a regular webserver instead, you're Standalone. The presence of a `docker-compose.yml` file alone doesn't tell you anything, the standard install pulls it from the repo either way.
If you're not sure which setup you're using, run `docker compose ps` in your Pelican directory. If it shows a running panel/web container, you're using Docker. Otherwise, you're using Standalone. A `docker-compose.yml` file alone doesn't indicate a Docker setup.
4 changes: 1 addition & 3 deletions web/docs/additional/migrations/pterodactyl.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,4 @@ A normal install on a Linux box, Pterodactyl running directly on the host. Head
Pterodactyl running inside Docker containers, with a `docker-compose.yml` somewhere. Head to the [Dockerized](./pterodactyl/docker.md) guide.
::::

If you're not sure which you have, check whether there's a `docker-compose.yml` file in your Pterodactyl directory. If there is, you're Dockerized; if not, you're Standalone.

If you're not sure which you have, check what's actually running. Run `docker compose ps` in your Pterodactyl directory: if it lists an active panel/web container, you're Dockerized. If the panel is served by a regular webserver instead, you're Standalone. The presence of a `docker-compose.yml` file alone doesn't tell you anything, the standard install pulls it from the repo either way.
If you're not sure which setup you're using, run `docker compose ps` in your Pterodactyl directory. If it shows a running panel/web container, you're using Docker. Otherwise, you're using Standalone. A `docker-compose.yml` file alone doesn't indicate a Docker setup.
Loading