2018-02-17 11:05:28 +08:00
|
|
|
# So you want to make an Egg
|
|
|
|
|
|
|
|
|
|
## General rules
|
|
|
|
|
|
2018-03-10 02:26:58 +08:00
|
|
|
1. Keep it simple.
|
2018-02-17 11:05:28 +08:00
|
|
|
We don't need 8 miles of install script
|
2018-03-10 02:26:58 +08:00
|
|
|
2. Keep it Small.
|
2018-02-17 11:05:28 +08:00
|
|
|
Only use what is absolutely needed.
|
2018-03-10 02:26:58 +08:00
|
|
|
3. Try to stay in the stock containers.
|
|
|
|
|
If you need something in a container PR it to [my image repo](https://github.com/parkervcp/images) where I can review and pull up to the main repo.
|
2018-02-17 11:05:28 +08:00
|
|
|
|
|
|
|
|
## Step 1.
|
|
|
|
|
#### Be aware of the pterodactyl install process.
|
|
|
|
|
|
|
|
|
|
The Pterodactyl install process is fairly simple once you know.
|
|
|
|
|
|
|
|
|
|
1. Spin up install container
|
|
|
|
|
This uses a volume mount on /mnt/server for the server files.
|
|
|
|
|
This can pull or set up all that is needed to run the server.
|
|
|
|
|
It is regularly used to just download the files required. Such as server files and configs.
|
|
|
|
|
|
|
|
|
|
2. Stop install container
|
|
|
|
|
|
|
|
|
|
3. Start a new container with the server files in /home/container
|
|
|
|
|
This is where the server is actually run.
|
|
|
|
|
Any dependencies installed during the install process are gone.
|
|
|
|
|
The container that is started should have everything you need.
|
|
|
|
|
|
|
|
|
|
## Step 2.
|
|
|
|
|
#### Testing
|
|
|
|
|
|
|
|
|
|
Make sure your install process is rock solid as I will be testing eggs before they ever hit my repo.
|
|
|
|
|
|
|
|
|
|
I will make sugestions and changes at will.
|
|
|
|
|
This is to maintain a clean repo that others can pull and be fully aware of what is being done.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## Step 3.
|
|
|
|
|
#### Don't be afraid to submit PR's to the egg repo.
|
|
|
|
|
|
2018-03-10 02:26:58 +08:00
|
|
|
I dont bite. I will work with you on the egg and the required things to run it.
|
