04a) Creating the config.yml
Last updated
Last updated
For this section, we'll create a proper 'config.yml' file for our 'pt-wings' container. Fortunately, the Pterodactyl Panel does the majority of the legwork for us. We only need to make a minor change because the default ports it wants to use for game servers are usually already in use by Docker or other Docker containers.
Head to the Configuration tab of your newly created Node:
This will contain your node's unique config.yml file. This is required for the pt-wings to function properly and to communicate with the Panel.
In my case, it looks like this:
Do not copy this specific text example to your config.yml - it'll not work.
You need to use the text from your panel!
Copy the config.yml into your text-editor of your choice.
At the bottom, below the remote: part, you need to add this:
This will cause the pt-wings to create a new network called pterodactyl_nw, which will be used by all game servers. It also uses a port range that is quite different from what Docker uses by default.
Remember to change the allowed_origins URL, to the URL of your panel!
In my case, I would enter pt-panel.engels.zip without http or https.
In my case, after I added the extra text, my config.yml will look like this:
config.yml the right wayTo get this file onto the server, place it in the /etc/pterodactyl directory as the root user, or with sudo.
To achieve this, I'll simply just use Nano and paste the text in there. Use this command:
Paste the text into the terminal, press CTRL-X to finish editing, then Y to confirm and ENTER to save.
Looks like this from a terminal point of view
Now we can continue to the next step
