homestead

问题 I installed a year ago Homestead with Laravel 5.5. Now I want to upgrade to Laravel 5.6. I upgraded Homestead as explained here with vagrant box update git pull origin master This forced me also to upgrade my vagrant to 2.1.2 . Now when I log in with vagrant ssh I cannot upgrade to Laravel 5.6, because when I run composer update I get this warning: Loading composer repositories with package information Updating dependencies (including require-dev) Your requirements could not be resolved to an

问题 When I run vagrant share id-goes-here --http 80 , the terminal gets stuck and it does not show me a URL: ==> homestead-7: Detecting network information for machine... homestead-7: Local machine address: 127.0.0.1 homestead-7: homestead-7: Note: With the local address (127.0.0.1), Vagrant Share can only homestead-7: share any ports you have forwarded. Assign an IP or address to your homestead-7: machine to expose all TCP ports. Consult the documentation homestead-7: for your provider (

问题 I edited the shared folder mapping rules in my Homestead.yaml file (C:\Users\username\.homestead). Then, I entered "vagrant halt" command to shut down vagrant. Then, I entered "vagrant up". However, the edits that I made to the folder mapping are not reflected in the virtual environment. It's as if my changes were not made at all in the Homestead.yaml file. How do I make the vagrant virtual environment reflect the changes that I made to the Homestead.yaml file? 回答1: You should reload using

问题 I'm working on a node project on my vagrant laravel/homestead box. Everything works fine, I can access the project when I go to the host define in my /etc/hosts : 192.168.10.10 project But, I'm trying to build and watch my project with webpack, so I installed webpack-dev-server and I can run it : http://localhost:8080/ webpack result is served from / content is served from /home/vagrant/Workspace/Kanban 404s will fallback to /index.html [...] webpack: bundle is now VALID. My problem is, when

问题 Homestead version: 2.0.7 Laravel version: 4.2.16 I'm just starting to learn Laravel, and I'm confused about the difference between environment configurations with start.php and homestead.yaml. Here's what I have: start.php: $env = $app->detectEnvironment(array( 'local' => array('josh-linux'), 'production' => array('homestead') )); homestead.yaml: variables: - key: APP_ENV value: testing123 If I run 'php artisan env' in the terminal it says 'local', and if I ssh into my homestead box and run

问题 I am running a Laravel Homestead Vagrant box on Windows 10 host. Currently, I am compiling assets (running npm run dev ) inside the vm. It's pretty slow at times, and I usually have problems with symlinks, running watchers etc. - in short, there is more configuration required that I think is necessary, Would it be better to compile assets directly on the host (Windows) machine? Are there any 'gotchas' I should have in mind? Does it really matter on what machine JavaScript assets are compiled?

问题 I get this error message when I try to vagrant up in my git-bash. $ vagrant up Bringing machine 'default' up with 'virtualbox' provider... ==> default: Importing base box 'laravel/homestead'... ==> default: Matching MAC address for NAT networking... ==> default: Checking if box 'laravel/homestead' is up to date... ==> default: Setting the name of the VM: homestead-7 ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration.

问题 I used laravel as backend (that implemented at homestead - mydomain.test) and angular 4 as frontend (that implemented at http://localhost:4200), now, I want to set a cookie from backend to frontend browser. Backend Controller: return response(['access_token'=>$response['access_token'], 'expires_in' => $response['expires_in']]) ->withCookie($cookie); and response is: Access-Control-Allow-Origin:* Cache-Control:no-cache, private Connection:keep-alive Content-Type:application/json Date:Sat, 30

问题 I'm running Laravel Homestead (Vagrant) on Windows 10. I'd like to be able to use other devices on my LAN to test my Homestead site too. (My LAN also has a Mac and an iPhone.) I found two ancient questions (1 and 2) that seem related to my goal, but I'm still stuck. I've tried adding a public_network config to my Homestead.yaml according to the docs (https://laravel.com/docs/5.4/homestead#network-interfaces). I've tried editing the homestead.rb file directly, too (but that didn't seem to help

问题 I'm a computer science graduate. I have just started an internship at a company where they use Laravel. My first task was to install Homestead. I did that. My second task is to create a shared folder between Homestead and my local machine (I have a macbook pro). I had a quick look on Laravel documentation but I didn't find any article related directly to this subject. Can somebody help me on this subject? (How can I create a shared folder between Homestead and my local machine?) 回答1: Don't