I was trying to update my MacBook to the newest version.
Also downloaded and installed the newest version of homestead, virtualbox and vagrant.
I also destroyed my old virtual machines and wanted to start fresh.
I had a couple of problems to get all of them to run again. But now, i got the machine running (vagrant up). At the end i get this error, but dont know what exactly i have to do:
homestead-7: Updating to version 1.8.3 (stable channel).
homestead-7:
homestead-7:
homestead-7: [ErrorException]
homestead-7: rename(/home/vagrant/.composer/cache/composer-temp.phar,/usr/local/bin/composer): Permission denied
homestead-7:
homestead-7:
homestead-7: self-update [-r|--rollback] [--clean-backups] [--no-progress] [--update-keys] [--stable] [--preview] [--snapshot] [--set-channel-only] [--] [<version>]
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
Also, i configured my paths in homestead.yaml like this:
---
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: testen.app
to: /home/vagrant/Code/testen/public
also configured it in the hosts. But when i open the link in my browser, it just says "No input file specified."
I log via vagrant ssh to the machine and check the path. It is there.
maybe getting no input file because of the previous error? I really don't know what i have to repair...
Are you sure that the composer.phar file is present? Check your access rights?
Related
I'm trying to set up laravel 5.5 working with homestead.
I've followed the steps here up to and including launching the vagrant box.
However, typing "dev.todoparrot.com" or "192.168.10.10" into browser brings up "No input file specified." error.
Trying
vagrant up --provision
(since I made changes to homestead.yaml) did not fix it.
My homestead.yaml looks like:
ip: "192.168.10.10"
memory: 2048
cpus: 1
provider: virtualbox
authorize: C:/Users/User/.ssh/id_rsa.pub
keys:
- C:/Users/User/.ssh/id_rsa
folders:
- map: D:/projects/todoparrot
to: /home/vagrant/Code
sites:
- map: dev.todoparrot.com
to: /home/vagrant/Code/todoparrot/public
I've installed laravel 5.5 into "D:/projects/todoparrot" with composer. Running php artisan serve on this folder works normally - template site is found at http://127.0.0.1:8000/.
Running
vagrant ssh
or Putty and navigating to /Code and typing ls returns the same files that are in "D:/projects/todoparrot", so the sync is working.
Changing
sites:
- map: dev.todoparrot.com
to: /home/vagrant/Code/todoparrot/public
to
sites:
- map: dev.todoparrot.com
to: /home/vagrant/Code/public
fixed my problem. Following tutorial without thinking about what I'm doing was the root of my mistake.
I installed Laravel with Homestead and tried to start a project that I created. Therefore I adjusted the Homestead.yaml to:
ip: "192.168.10.10"
memory: 2048
cpus: 1
provider: virtualbox
authorize: ~/.ssh/id_rsa.pub
keys:
- ~/.ssh/id_rsa
folders:
- map: ~/Documents/Development/Source/MFServer/
to: /home/vagrant/Code
sites:
- map: local.medifaktor
to: /home/vagrant/Code/MFServer/public
The path is existing but still I get this error message. Can you give me some advice?
I think this only works when you need to reload the file and there is no other problems.
From Jesús' site: http://www.jesusamieiro.com/no-input-file-specified-using-homestead/
“No input file specified” using Homestead - Posted on 02/06/2016
If you see the message “No input file specified” in the browser (using Homestead as development VM machine), one possible problem is that Homestead doesn’t load the parameters from the config file Homestead.yaml
Try to provision the VM another time, running
$ vagrant reload --provision
Been trying this for days! I am aware there are other Qs about this, which I have checked over an over. I have one site working and the other not.
I'm using Homestead with Laravel 5 and OSX 10.10.3
I have this .yaml file:
---
ip: "192.168.10.10"
memory: 2048
cpus: 1
provider: virtualbox
authorize: ~/.ssh/id_rsa.pub
keys:
- ~/.ssh/id_rsa
folders:
- map: ~/Sites/LaraCode
to: /home/vagrant/LaraCode
sites:
- map: myapp.app
to: /home/vagrant/LaraCode/myapp/public
- map: newapp.dev
to: /home/vagrant/LaraCode/newapp/public
databases:
- homestead
variables:
- key: APP_ENV
value: local
Both are Laravel 5 apps in these folders:
/Users/USERNAME/Sites/LaraCode/myapp
/Users/USERNAME/Sites/LaraCode/newapp
myapp.app works fine but newapp.dev gives an error:
No input file specified
in the browser.
I have chmod777 the storage folder. There is an index.php in the public folder. I vagrant provision after changes.
Homestead seems to have been a horrible waste of time.
For me homestead destroy and another homestead up worked. Also I guess you added the new url to you hosts file, correct?
Although I agree that the docs for homestead are a little lacking.
Ok,I finally found an answer for this. I believe I had two homesteads set up, so I had to remove a homestead from the VM
I also had to do update my bash_profile so I could use the homestead commands.
Afterwards, in the homestead folder I ran:
homestead provision
To ensure the yaml file was up-to-date.
All is good now. Both sites are running. Server set-ups are always a nightmare for the less computer techie developers. Where I was caught out was the lack of clear folder guidance on where to execute command lines, hence the conflicting homesteads.
This question already has answers here:
Error when trying vagrant up
(26 answers)
Closed 8 years ago.
I am learning to use vagrant and I have recently a setup vagrant homestead system on my local machine.
my homestead.yaml is in scr/stubs/ folder.
It looks like this.
ip: "192.168.10.10"
memory: 2048
cpus: 1
authorize: /var/www/myhomestead/homestead/ssh/id_rsa.pub
keys:
- /var/www/myhomestead/homestead/ssh/id_rsa
folders:
- map: /var/www/sites/
to: /home/vagrant/sites/
sites:
- map: homestead.app
to: /home/vagrant/Code/Laravel/public
databases:
- homestead
variables:
- key: APP_ENV
value: local
When I run "vagrant up" it gives me errors like this.
amit#Amit:/var/www/myhomestead/homestead$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'base' could not be found. Attempting to find and install...
default: Box Provider: virtualbox
default: Box Version: >= 0
==> default: Adding box 'base' (v0) for provider: virtualbox
default: Downloading: base
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.
Couldn't open file /var/www/myhomestead/homestead/base
You can try vagrant init hashicorp/precise32. This creates the box not just the project.
Then do vagrant up to get the ball rolling.
Newbie to laravel homestead and vagrant and struggling to get my site to load in the browser. Everything looks as though its running, successfully ran vagrant up.
When i type url http://local.bookings.com:8000/ I receive message "This webpage is not available"
I should point out however that I am on Windows 7 and have nothing visibly running in Oracle VM VirtualBox Manager.
Homestead.yaml
ip: "192.168.10.10"
memory: 2048
cpus: 1
authorize: c:/Users/me/.ssh/github_rsa.pub
keys:
- c:/Users/me/.ssh/github_rsa
folders:
- map: /Users/me/documents/projects/bookings
to: /home/vagrant/Code
sites:
- map: local.bookings.com
to: /home/vagrant/Code/bookings/public
variables:
- key: APP_ENV
value: local
hosts file
127.0.0.1 local.bookings.com
Edit the host file as
192.168.10.10 local.bookings.com
Hope this will work.
I had this problem, make sure you run homestead up or vagrant up and change the host file to 192.168.10.10 local.bookings.com