pterodactyl
Here are 50 public repositories matching this topic...
-
Updated
Oct 2, 2020 - Shell
-
Updated
Sep 9, 2020 - JavaScript
-
Updated
Oct 4, 2020 - Go
-
Updated
Sep 29, 2020 - PHP
-
Updated
Sep 21, 2020 - JavaScript
-
Updated
Oct 4, 2020 - Vue
-
Updated
Aug 26, 2020
-
Updated
Oct 5, 2020 - PHP
Reference the tfstate file for hosts that were created on the Google Cloud platform. In that file
- Identify the the Terraform Provider name.
- Develop a JSON path that returns the hostnames contained in the tfstate file
- Update HELPER_HOSTNAME_QUERY_MAP in config.yaml
- the query map is a list of Key:Value pairs
- Use the provider name for the Key
- Use the JSON path for the Value
-
Updated
May 4, 2020 - Shell
-
Updated
Sep 17, 2020 - Shell
-
Updated
Oct 9, 2017 - Java
-
Updated
Aug 8, 2018 - PHP
-
Updated
Aug 1, 2020 - TypeScript
-
Updated
Oct 1, 2020 - JavaScript
-
Updated
Sep 14, 2020 - Dockerfile
-
Updated
Aug 29, 2020 - Dockerfile
-
Updated
Mar 25, 2020 - Java
-
Updated
Aug 9, 2020 - Shell
-
Updated
Jun 16, 2020 - Shell
-
Updated
Nov 26, 2019 - Shell
-
Updated
Oct 2, 2020 - JavaScript
-
Updated
Sep 18, 2020 - Shell
Improve this page
Add a description, image, and links to the pterodactyl topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the pterodactyl topic, visit your repo's landing page and select "manage topics."


The name "CPU Threads" has lead to confusion twice today, and it actually is confusing. It sounds like it's the amount of CPU threads the server can use, not which specific (multi threaded) cores the server will use.
I suggest renaming it to "CPU Pinning", as that's more correct, and less likely to fall victim to "oh, I don't really know what I'm doing but my server needs all the performance it