pterodactyl/development
1
0
Fork 0
mirror of https://github.com/pterodactyl/development.git synced 2025-12-10 10:44:48 -06:00
Code Issues Packages Projects Releases Wiki Activity

add info on daemons to readme, also y

Browse Source
This commit is contained in:
Jakob Schrettenbrunner 2019-02-02 14:01:27 +01:00
parent f99509305c
commit ec9d4d645c
2 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
README.md
View File

@ -20,5 +20,8 @@ vagrant up --provision-with setup app
### Subsequent Runs
Once you already have everything setup for the app, you can simply run `vagrant up`. If you only need the application, and have your own SQL server, redis, and mailhog (or some combination), you can run `vagrant up [boxes]` and replace `[boxes]` with the boxes to bring online.
### Daemons
There are VMs for both, the old and the new, daemons configured. They do not start automatically. You can start them using `vagrant up daemon` (for the nodejs one) and `vagrant up wings` (the golang one).
### Updating /etc/hosts
On your first run, and whenever the hostnames change, you'll have to run `vagrant hostmanager app --provider docker` to update your /etc/hosts file.

2
Vagrantfile vendored
View File

@ -157,7 +157,7 @@ Vagrant.configure("2") do |config|
# Create a docker container for mailhog which providers a local SMTP environment that avoids actually
# sending emails to the address.
config.vm.define "mailhog" do |mh|
mh.vm.hostname = "mailhog.pterodactl.test"
mh.vm.hostname = "mailhog.pterodactyl.test"
mh.vm.synced_folder ".", "/vagrant", disabled: true
mh.vm.network "forwarded_port", guest: 1025, host: 1025