B
B
BonBon Slick2017-09-19 20:13:34
Vagrant
BonBon Slick, 2017-09-19 20:13:34

Vagrant - No input file specified, view not found, port + cache issue?

Windos 10 Pro, Installed Vagrant + Homestead, set it up for a day because nothing wanted to work, even now there were still bugs with ports where it is not clear how the forward goes from 54320 to 5432 which goes to 54320, so php artisan migrate did not work, etc. d. However, okay, it's not so important, each time creating migrations add 54320 instead of 5432, and everything worked.

Today I made edits in the project code, an error occurred:
View [home] not found

Very strange, since a second ago, as in principle, and a few days before that, everything worked fine. Akey, they advised me to clear the cache, I’ll tell you right away, I tried it via ssh in phpStorm and cmd windows, in a different order

php artisan config:cache
php artisan config:clear
composer update
php artisan cache:clear;
php artisan optimize;
composer dump-autoload;
php artisan route:clear"


Knocked out an error that the view was found, no matter how and through how it was not introduced.
Completely cleared the browser cache. Deleted the sessions, view, cache folders in storage/framework.

I don't understand what's wrong again? Why did it fly off? What's up with Vagrant?

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: laravel.app
      to: /home/vagrant/Code/public
      schedule: true
      php: "7.1"

databases:
    - namedb

variables:
    - key: APP_ENV
      value: local

I tried to edit the paths to the project files, although it is unlikely that there was an error in this, because everything worked more or less. Actually nothing has changed.

In addition to the fact that after vagrant provision it generally gives an error.
No input file specified.

I noticed that many people have problems with Vagrant, although it is so much promoted on Larvel's podcasts and generally everywhere, while I received many times more errors from it than from XAMPP or OpenServer.
Reinstalling Vagrant is not an option, it will take a long time, again. https://laravel.io/forum/06-04-2014-no-input-file-...
PC restarted, --prision did, vagrant halt / up didn't help either.
hosts file is ok
192.168.10.10 laravel.app

Answer the question

In order to leave comments, you need to log in

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question