Creating servers in Pterodactyl: Difference between revisions

No edit summary
add
Line 1: Line 1:
{{Construction}}
{{Construction}}
{{Ambox|type=|image=|text=Please note:
{{Ambox|type=|image=|text=Please note:
* The spinning up a server, regardless if we already have the egg, '''requires Fleff's approval''' as it consumes resources.
* The spinning up a server '''requires Fleff's approval''' as it consumes machine resources.
* The spinning up of a server necessitates '''administrator privileges''' on the Pterodactyl panel. At present, only <code>@SYS:OP</code> members have this.
* The spinning up of a server necessitates '''administrator privileges''' on the Pterodactyl panel. At present, only <code>@SYS:OP</code> members have this.
}}
}}


This guide will go over how to create a new server on the Pterodactyl panel.
This guide will go over how to create servers on Pterodactyl.


== Eggs ==
This guide will refer to eggs frequently. An ''egg'' is a file which tells Pterodactyl ''how'' to install, launch, and manage whatever application the egg is advertising. It tells Pterodactyl what commands to execute to download the software, setup it's environment, and what configuration options should be available to server operators.<ref>For example, for the Arma server, it's egg tells Pterodactyl's GUI to provide an option to change the server's modlist. It maps the input made on the GUI to the relevant configuration file on the server.</ref>


As all servers are different, so to are not all egg installations the same. ''Some'' degree of basic server and computer literacy will be necessary. This guide will aim to be as helpful as possible in spite of this.
== Footnotes ==
{{Reflist}}
[[Category:Systems management]]
[[Category:Systems management]]