So I am trying to setup homestead on my windows machince but I keep getting the 'No input file specified' but im prettu sure I got the path corretly because they where working before. My homestead yaml file is like the following.
folders:
- map: C:\Users\Steve\Dropbox\Work\Laravel
to: /home/vagrant/Code/
sites:
- map: homestead.app
to: /home/vagrant/Code/Laravel/public
Now the files are syncing between one another and inside of Laravel I have another Laravel folder which contains the frameowrk.
When i run homestead.app I get the error and as you can see in the screenshot below the paths are matching together. If you shed some light I would greatly appreciate.
I have tried homestead destroy and homestead destroy multiple time.
Related
I'm trying to install Homestead on a Mac using VirtualBox and when I edit the homstead.yaml file to change the location of my local shared folder the change never registers, as I always get the error
The host path of the shared folder is missing: ~/Code
when I vagrant up.
When I performed bash init.sh I was asked to overwrite homestead.yaml, after.sh, and aliases. I've been having this problem for a while now and have tried many different things but nothing seems to work. I new with Laravel and would appreciate some help. Thanks!
In your Homested.yaml file but make sure you have folder in your C:\Code
folders:
- map: C:/Code
to: /home/vagrant/Code
sites:
- map: homestead.app
to: /home/vagrant/Code/Laravel/public
Changed the application folder names in question to application1/application2 just for the purposes of this question.
If it makes any difference, I am using Homestead/Vagrant/VirtualBox.
In my homestead.yaml, I have this:
folders:
- map: ~/Homestead/Projects
to: /home/vagrant/Sites
sites:
- map: application1.app
to: /home/vagrant/Sites/application1/public
- map: application2.app
to: /home/vagrant/Sites/application2/public
In my hosts file, I have this:
127.0.0.1 application1.app application2.app
192.168.10.10 application1.app application2.app
When I just had the application1.app on both the homestead.yaml and hosts file, all was fine and dandy. Everything is still fine and dandy, however when I try to go to application2.app, it goes to the project in application1.app.
I tried flushing my DNS cache, no luck.
I tried vagrant --provision, no luck.
Can anyone please explain to me what I'm, doing wrong?
For anyone with this problem
Solved this with vagrant provision. My other method of vagrant --provision didn't work because there is no provision flag (according to freenode #laravel irc), so that must be for an older version - not Laravel 5.
I am new on vagrant. I am using Laravel Homestead Improved by following this
link. I want to map my existing code on vagrant which is inside my xampp installation. Here is my Homestead.yaml file contents.
ip: "192.168.10.10"
memory: 2048
cpus: 1
sites:
- map: myapp.com
to: /home/vagrant/Code
folders:
- map: /opt/lampp/htdocs/codebase
to: /home/vagrant/Code
variables:
- key: APP_ENV
value: local
Although when I run the following command
cd Code/
it shows my code but on browser when I run http://myapp.com:8000/ it shows "No input file specified."
By default a webserver usually looks for index.html then index.php, neither of these files are in your /home/vagrant/Code folder which is why you're getting the "No input file specified" error.
On your sites section, you should map the domain to your public folder of Laravel. So in this case it should likely be /home/vagrant/Code/public
You mapped codebase to Code, and you mapped myapp.com to Code.
If you currently have an app in codebase/app1/index.php, then this wouldn't work because myapp.com is looking for index.php inside Code.
Thus, you need to access either: myapp.com:8000/app1 OR you need to remap sites like so (and do this for every site/app folder inside codebase):
sites:
- map: myapp.com
to: /home/vagrant/Code/app1
Note that you need to replace app1 with whatever you called your app's folder in XAMPP
I think I finally got homestead installed on my laptop! Now, I am trying to view my laravel project in the browser.
When I open "dev.app" in the browser I get a message that say "No input file specified." which I think means that my homestead is working but the laravel project is not there/setup.
I have created a folder called Projects on my local laptop (i.e. ~/Projects). Then from inside of it i executed this command
laravel new dev
But I still get the same error message in the browser i.e. "No input file specified." I have also tried to open this link "dev.app"/dev" but I still get the same message.
What I am doing wrong?
Here is the content of my 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: ~/Projects
to: /home/vagrant/Code
sites:
- map: dev.app
to: /home/vagrant/Code/Laravel/public
databases:
- homestead
variables:
- key: APP_ENV
value: local
Additional, when I execute the following 2 commands in order
cd ~/Projects
ls
I see the following directories dev homestead
What should I do to see my project when I go to dev.app ? Do I need to do anything from my Ubuntu VM or I should be able to edit the files directly in located on ~\Projects\dev" from my laptop?
Add an entry in /etc/hosts on your local machine
192.168.10.10 dev.app
Correct the path to the public folder in the sites section of your Homestead.yaml
sites:
- map: dev.app
to: /home/vagrant/Code/dev/public
I have just made the following Homestead.yaml file:
authorize: ~/.ssh/id_rsa.pub
keys:
- ~/.ssh/id_rsa
folders:
- map: ~/GIT/old-project
to: /home/vagrant/old-project
- map: ~/GIT/project
to: /home/vagrant/project
sites:
- map: old-project.app
to: /home/vagrant/old-project/public
- map: project.app
to: /home/vagrant/project/public
databases:
- name: old-project
- name: project
variables:
- key: APP_ENV
value: local
old-project already existed. Next I ran vagrant up, then vagrant ssh then inside the vagrant box I ran composer create-project laravel/laravel project 4.2 --prefer-dist. Laravel installed. I edited my /etc/hosts file and now project.app leads me to the Laravel 'You have arrived' page. Great – everything works.
But on my mac, the folder ~/GIT/project is empty.
What part of the installation process did I miss? Is there anything I've done wrong that has prevented the files from mapping across correctly?
If I open ~/GIT/old-project all the Laravel files are there, and it works as I'd expect. I can't remember any difference in how I set up that project.
I guess you should run the vagrant provision command, to make the added directory (~/GIT/project) shared with the homestead.
When you run the command vagrant up for the first time, the directory ~/GIT/old-project became shared with the homestead. However the directory ~/GIT/project is not shared therefore it is empty on your mac.
Note: When running the provision command, your existing databases will be destroyed and recreated.