Creating servers in Pterodactyl: Difference between revisions

No edit summary
No edit summary
Line 7: Line 7:


== Eggs ==
== Eggs ==
An ''egg'' is a Pterodactyl-specific configuration file which tells Pterodactyl ''how'' to install, launch, and manage a particular application autonomously. It also sets what configuration options are available to operators in the panel itself.<ref>For example, for the Arma server, it's egg is configured to give operators an option in the panel to change the server's active modlist. The egg maps this created option to the appropriate line on Arma's <code>server.cfg</code> file.</ref>
An ''egg'' is a file which tells Pterodactyl ''how'' to install a particular application, and then Pterodactyl executes those instructions inside a docker container, with Pterodactyl providing an interface to manipulate it. The egg also translates application-specific settings (e.g. setting player slots for a ''Garry's Mod'' server) as configurable options in the panel.


While the adding of a new egg to the panel is always the same, because by their nature all game servers<ref>Pterodactyl can be used for non-game servers too, like [https://foundryvtt.com/ FoundryVTT] or TeamSpeak, but the point stands.</ref> are different, the configuration and effort required to get a server to launch for the first time is case-by-case.
While the adding of a new egg to the panel is always the same, because by their nature all game servers<ref>Pterodactyl can be used for non-game servers too, like [https://foundryvtt.com/ FoundryVTT] or TeamSpeak, but the point stands.</ref> are different, the configuration and effort required to get a server to launch for the first time is case-by-case.