ThunderNetworkRaD/yolks
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Add more notes and details for contributing.

Browse source
This commit is contained in:
Dane Everitt 2021-05-15 12:54:01 -07:00
parent a34778013d
commit e4e52642d2
1 changed files with 15 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
README.md
View file

@ -2,12 +2,22 @@
A curated collection of core images that can be used with Pterodactyl's Egg system. Each image is rebuilt A curated collection of core images that can be used with Pterodactyl's Egg system. Each image is rebuilt
periodically to ensure dependencies are always up-to-date. periodically to ensure dependencies are always up-to-date.
Images are hosted on both `ghcr.io` and `quay.io` for redundancy. To use any of these images, use Images are hosted on `ghcr.io` and exist under the `games`, `installers`, and `yolks` spaces. The following logic
`ghcr.io/pterodactyl/yolks:<IMAGE>` or `quay.io/pterodactyl/yolks:<IMAGE>`. is used when determining which space an image will live under:
Any images ending with `-install` should only be used as a install image for running an install script, these images * `games` — anything within the `games` folder in the repository. These are images built for running a specific game
will not work to run the actual server and are only designed to reduce installation time and network usage by or type of game.
pre-installing common installation dependencies such as `curl` and `wget`. * `installers` — anything living within the `installers` directory. These images are used by install scripts for different
Eggs within Pterodactyl, not for actually running a game server. These images are only designed to reduce installation time
and network usage by pre-installing common installation dependencies such as `curl` and `wget`.
* `yolks` — these are more generic images that allow different types of games or scripts to run. They're generally just
a specific version of software and allow different Eggs within Pterodactyl to switch out the underlying implementation. An
example of this would be something like Java or Python which are used for running bots, Minecraft servers, etc.
All of these images are available for `linux/amd64` and `linux/arm64` versions, unless otherwise specified, to use All of these images are available for `linux/amd64` and `linux/arm64` versions, unless otherwise specified, to use
these images on an arm system, no modification to them or the tag is needed, they should just work. these images on an arm system, no modification to them or the tag is needed, they should just work.
### Contributing
When adding a new version to an existing image, such as `java v42`, you'd add it within a child folder of `java`, so
`java/42/Dockerfile` for example. Please also update the correct `.github/workflows` file to ensure that this new version
is tagged correctly.