For whatever reason I cannot get multiple sites to work with Homestead. Every new site added, returns the same site when I visit it in the browser
I have tried every "solution" I have come across here on stack as well as on larvel.io. None of them solve the problem. Any help would be greatly appreciated.
Below are the contents of both my .yaml file and my hosts file.
Local Directory Structure:
Root directory = WWW
project1 = WWW/project1
project2 = WWW/project2
Homestead.yaml:
---
ip: "192.168.10.10"
memory: 2048
cpus: 1
provider: virtualbox
authorize: ~/.ssh/id_rsa.pub
keys:
- ~/.ssh/id_rsa
folders:
- map: ~/WWW
to: /home/vagrant/Code
sites:
- map: /project1.app
to: /home/vagrant/Code/project1/public
- map: /project2.dev
to: /home/vagrant/Code/project2/public
databases:
- project1_db
- project2_db
variables:
- key: 'APP_ENV'
value: 'local'
- key: 'APP_DEBUG'
value: 'true'
# blackfire:
# - id: foo
# token: bar
# client-id: foo
# client-token: bar
# ports:
# - send: 93000
# to: 9300
# - send: 7777
# to: 777
# protocol: ump
/etc/hosts file:
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting. Do not change this entry.
##
127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost
192.168.10.10 project1.app
192.168.10.10 project2.dev
I have tried the following:
vagrant provision
vagrant reload --provision
Destroyed box and vagrant up
vagrant global-status, followed by vagrant provision vm#
have also tried to map folders and sites
ex:
folders:
- map: ~/WWW/project1
to: /home/vagrant/Code/project1
- map: ~/WWW/project2
to: /home/vagrant/Code/project2
sites:
- map: /project1.app
to: /home/vagrant/Code/project1/public
- map: /project2.dev
to: /home/vagrant/Code/project2/public
First, one tip: use nfs because windows folder share is very very slow. To add support for this feature on Windows you should install vagrant-winnfsd
vagrant plugin install vagrant-winnfsd
folders:
- map: ~/WWW
to: /home/vagrant/Code
type: nfs
Just in case remove the slash before the site hostname. I don't have sure if this is the reason but was the only thing wrong I found in your configuration.
sites:
- map: project1.app
to: /home/vagrant/Code/project1/public
- map: project2.dev
to: /home/vagrant/Code/project2/public
Another tip: install the vagrant-hostsupdater plugin to add the hostnames to your hosts file automatically.
vagrant plugin install vagrant-hostsupdater
in you Homestead.yaml file:
aliases: ["project1.app", "project2.dev"]
in scripts/homestead.rb file:
config.hostsupdater.aliases = settings["aliases"]
My files: homestead.rb and Homestead.yaml
Got it.
The slashes before the domain where causing the issue.
Changed this:
sites:
- map: /project1.app
to: /home/vagrant/Code/project1/public
- map: /project2.dev
to: /home/vagrant/Code/project2/public
To this:
sites:
- map: project1.app
to: /home/vagrant/Code/project1/public
- map: project2.dev
to: /home/vagrant/Code/project2/public
Related
I have searched and tried everywhere for something that might fix this but whenever I have a new homestead code folder, it doesn't work when I use vagrant and virtualbox. I have checked my hosts files and every file. No error shows up but it clearly doesn't work. I have also enabled virtualization on my CPU. Below is my current homestead.yaml file
---
ip: "192.168.10.10"
memory: 2048
cpus: 2
provider: virtualbox
folders:
- map: C:/Laravel/code
to: /home/vagrant/code
sites:
- map: homestead.test
to: /home/vagrant/code/homestead/public
- map: homestead1.test
to: /home/vagrant/code/homestead1/public
- map: coursework.test
to: /home/vagrant/code/coursework/public
databases:
- homestead
features:
- mariadb: false
- ohmyzsh: false
- webdriver: false
# ports:
# - send: 50000
# to: 5000
# - send: 7777
# to: 777
# protocol: udp
I am trying to just get coursework.test to work but I'm sure its wrong on both of them
Your problem is in the way you use your slashes.
- map: C:/Laravel/code
has to be
- map: C:\Laravel\code
Another problem you will be walking against is that you do not have a database.
Enable mariadb or something else in your features tab
First off: I'm new to using Laravel. I got the homestead VM up and running with Vagrant. I checked my Homestead.yaml file and it checks out, did the additions to the hosts file as well, and created my blog according to the video tutorials on the VM.
When I run the command "php artisan serve" and try the address it returns, I get an error saying "No input file specified".
Anyone have a fix for this?
ip: "192.168.10.10"
memory: 2048
cpus: 1
provider: virtualbox
authorize: ~/.ssh/id_rsa.pub
keys:
- ~/.ssh/id_rsa
folders:
- map: /Users/JeromePapalie/LaravelCode
to: /home/vagrant/Code/Laravel
sites:
- map: homestead.app
to: /home/vagrant/Code/Laravel/public
databases:
- homestead
First, you need to check the folder structure.
This is my folder structure.
Here my Homestead.yaml file
---
ip: "192.168.10.10"
memory: 2048
cpus: 1
provider: virtualbox
authorize: /Users/kelvin/.ssh/kevin.pub
keys:
- ~/.ssh/kevin
folders:
- map: ~/Documents/Work/kevindev/Code
to: /home/vagrant/Code
sites:
- map: homestead.app
to: /home/vagrant/Code/Laravel/public
databases:
- homestead
# blackfire:
# - id: foo
# token: bar
# client-id: foo
# client-token: bar
# ports:
# - send: 50000
# to: 5000
# - send: 7777
# to: 777
# protocol: udp
Hope, you already generated ssh key file in your target folder something like this.
And then, open your host vim /etc/hosts and add your homestead.app host
Finally, go to your Homestead folder and type vagrant up command.
That's is.
I have installed vagrant on my machine. I have homestead installed both globally and in my project.
When I run vagrant up it does not work, I am unable to access the url in my browser, it comes up with a blank screen.
So I searched online and found a solution that allowed me to use homestead up by editing my ~/bash_profile and adding the following code:
function homestead() {
( cd ~/Workspace/homestead && vagrant $* )
}
Now when I navigate to my project director and run homestead up it works I am able to access the site via the url in my browser however I encountered another issue, it seemed to be loading from the global homestead.yaml file instead of my project's homestead.yaml file.
When I removed the site from my global homestead.yaml file and put it in my project's homestead.yaml file I kept getting no
input file specified
This is my project's homestead.yaml file:
---
ip: "192.168.10.10"
memory: 2048
cpus: 1
hostname: blog
name: blog
provider: virtualbox
authorize: ~/.ssh/id_rsa.pub
keys:
- ~/.ssh/id_rsa
folders:
- map: "~/Workspace/blog"
to: "/home/vagrant/workspace/blog"
sites:
- map: blog.app
to: "/home/vagrant/workspace/blog/public"
databases:
- blog
# blackfire:
# - id: foo
# token: bar
# client-id: foo
# client-token: bar
# ports:
# - send: 50000
# to: 5000
# - send: 7777
# to: 777
# protocol: udp
And this is my global homestead.yaml file:
---
ip: "192.168.10.10"
memory: 2048
cpus: 1
provider: virtualbox
authorize: ~/.ssh/id_rsa.pub
keys:
- ~/.ssh/id_rsa
folders:
- map: ~/Workspace
to: /home/vagrant/workspace
sites:
- map: homestead.app
to: /home/vagrant/workspace/Laravel/public
databases:
- blog
# blackfire:
# - id: foo
# token: bar
# client-id: foo
# client-token: bar
# ports:
# - send: 50000
# to: 5000
# - send: 7777
# to: 777
# protocol: udp
Don't forget to flag --provision after you edited your .yaml file, so
homestead up --provision
OR
homestead reload --provision
Furthermore in your global Homestead.yaml you're syncing also the Homestead folder with the virtual box, that doesn't make much sense.
I would leave that apart and change it's path to ~/Homestead/ so your ~/Workspace/ will contain only the projects.
so change your bash profile accordingly, and change your Homestead.yaml file to reflect this (if you want to run multiple projects on the same box you won't need "projet" yaml file, but just the hometead global yaml file):
folders:
- map: ~/Workspace
to: /home/vagrant/workspace
sites:
- map: homestead.app
to: /home/vagrant/workspace/Laravel/public
- map: blog.app
to: /home/vagrant/workspace/blog/public
Hope this help
Cheers
I just set up my vhost for testing purposes. I've been using vagrant before, but it was for symfony project. The problem is that my server doesn't respond.
my Homestead.yaml file:
---
ip: "192.168.10.10"
memory: 2048
cpus: 1
provider: virtualbox
authorize: ~/.ssh/trust_a_skill.pub
keys:
- ~/.ssh/trust_a_skill
folders:
- map: c:/xampp/htdocs/trust_a_skill
to: /home/vagrant/trust_a_skill
sites:
- map: trustaskill.local
to: /home/vagrant/trust_a_skill/public
databases:
- homestead
variables:
- key: APP_ENV
value: local
# blackfire:
# - id: foo
# token: bar
# client-id: foo
# client-token: bar
# ports:
# - send: 93000
# to: 9300
# - send: 7777
# to: 777
# protocol: udp
I also configuted my system(windows) host file
192.168.10.10 trustaskill.local
I already have tried curl'ing http://trustaskill.local:8000/ and 192.168.10.10
Any thoughts what Am i doing wrong here? I just followed documentation on laravel site. My ssh work's just fine. Thanks in advance!
do
vagrant provision
in your Homestead folder.
and you might want to check if you use tab instead of space in your Yaml file. Yaml file is so sensitive and it some issues with tabs.
After you edit the Homestead.yaml file you need to do
homestead provision
and edit your host file adding
192.168.10.10 trustaskill.local
in mac
sudo nano /private/etc/hosts
I'm trying to set up a homestead machine on my Windows8 PC, for Laravel development. I have managed to get the machine up and running, I can SSH into it.
But somehow visiting http://homestead.app doesn't work.
I returns "This web page is not available".
I added this line to my hosts file:
192.168.10.10 homestead.app
My Gitbash did say at a certain piont: "Warning: Connection timeout. Retrying..." But continued anyway.
This is how my Homestead.yaml looks like:
---
ip: "192.168.10.10"
memory: 2048
cpus: 1
provider: virtualbox
authorize: ~/.ssh/id_rsa.pub
keys:
- ~/.ssh/id_rsa
folders:
- map: ~/Code
to: /home/vagrant/Code
sites:
- map: homestead.app
to: /home/vagrant/Code/Laravel/public
databases:
- homestead
variables:
- key: APP_ENV
value: local
# blackfire:
# - id: foo
# token: bar
# client-id: foo
# client-token: bar
# ports:
# - send: 93000
# to: 9300
# - send: 7777
# to: 777
# protocol: udp
You can redirect your request to your host port and with your host machine you would be able to access you app.