To the box by using your own ssh key and b) letting vagrant use your private key (which might come in handy They are responsible for a) making it possible to connect If you already have an SSH key pair that is located in the `.ssh` folder in your home directory, you can leave the following lines in place: This should be the path to the `public` folder of the repository on your **vagrant machine** `to: "/home/vagrant/laravelexample/public"` denotes the absolute path within the vagrant box that the above mentioned hostname uses as lookup path for content. to laravelexample.app instead of homestead.app)Īlthough it not strictly necessary since nginx will respond to other hostnames as well You _should_ adjust that entry if you are going to have multiple projects (e.g. `map: homestead.app` denotes the hostname that the nginx is looking for to serve content on So that you can access your local files within the vagrant box. `to` denotes the path on your **vagrant** (remote) machine that is mapped to the above mentioned path on your local machine, `map` should point to the absolute path to the repository on your **local** (host) machine. ![]() This is the IP that is assigned to your virtual machine. make sure the `ip` (`192.168.10.10` in the example above) is not already used in your local network. There are a few things I would like to adjust: To: "/home/vagrant/laravelexample/public" map: "C:/Users/Pascal/PhpstormProjects/LaravelExample"
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |