Development environment setup for Pterodactyl. This is used internally by our development team to ensure getting Pterodactyl running in a development environment is a painless as possible.
This PR adds a VM for the nodejs daemon. It is a VM so we don't litter the host with docker containers created by the daemon, it's the same for wings. Both don't autostart.
The daemon VM also contains golang for the standalone sftp.
This PR also disables hostmanager by default and requires to run it manually.
The reason for this is that the hostmanager overrides /etc/hosts when starting the individual VMs and leaves out the docker containers' hostnames for whatever reason.
When using vagrant hostmanager app --provider docker it sets all hostnames correctly.
I've also set the various pterodactyl.test hostnames to everything directly to avoid useless entries in /etc/hosts and renamed pterodocs.test to docs.pterodactyl.test.
This also adds the nginx reverse proxy configuration to the app container's nginx, so docs.pterodactyl.test is actually reachable.
This PR adds a VM for the nodejs daemon. It is a VM so we don't litter the host with docker containers created by the daemon, it's the same for wings. Both don't autostart. The daemon VM also contains golang for the standalone sftp.
This PR also disables hostmanager by default and requires to run it manually. The reason for this is that the hostmanager overrides /etc/hosts when starting the individual VMs and leaves out the docker containers' hostnames for whatever reason. When using
vagrant hostmanager app --provider dockerit sets all hostnames correctly.I've also set the various pterodactyl.test hostnames to everything directly to avoid useless entries in /etc/hosts and renamed pterodocs.test to docs.pterodactyl.test.
This also adds the nginx reverse proxy configuration to the app container's nginx, so docs.pterodactyl.test is actually reachable.