I recently came back to laravel after having worked in another field for a few years now homestead was just not working on my windows machine anymore and never having used Docker before you were my little lifeline here thanks for a very well explained step by step here was very helpful.
Only minor thing I had to do was the alias was nice to have however after shutting down and starting up again I had the set the alias again so ended up going into ~/.bashrc and manuelly adding it that seems to have fixed it for me
Hi, how can I run via PHPStorm terminal symbolic link folder on Ubuntu and open files in PHPStorm with the possibility of running the sail command in the terminal after? (wsl2) ~/Projects > (windows) ~/Projects
Depending on the project, and the amount of data shared between the container(or VM) and host, I agree it can be too slow. And it also depends on how many times I need to refresh the browser, while developing.
the worst tutorial ever, saying you have 2 projects already in folder is not what we expect, do everything from scratch, and create them in video on the fly
I'm sorry that approach confused you. Having them pre-installed cut the video by 10 boring minutes. I was attempting to show the difference between Laravel apps with and without Sail installed, and I showed how to install Sail when not already installed. I hope that helps. Good luck with your learning.
I have been struggling to get docker and laravel working as well as understand everything. Even though some think this video is not detail enough there were enough things said that helped me out and was able to make more sense of everything. At the end of the day I was able to create a project and get docker up and running and the website responds in my local browser. Thanks.
Not the worst tutorial ever, but not very helpful for those of us who need to install Laravel Sail into an existing project. How did you possibly get Laravel Sail installed into your existing project? It requires you to have both PHP and COMPOSER installed in WSL2. That's an important thing to cover. Also, it requires all the PHP extensions that Laravel requires because COMPOSER will fail to install Sail unless all the extensions are present. If I'm going to have to to make WSL2 (Ubuntu) a complete Laravel development environment just to get to the point where I can install Sail, what is the point of Laravel Sail?
For a detailed video on installing WSL 2 (Windows Subsystem for Linux) see: th-cam.com/video/X3bPWl9Z2D0/w-d-xo.html
Or to see how to set up Laravel on WSL 2, see: th-cam.com/video/_H1iKXksjF0/w-d-xo.html
I recently came back to laravel after having worked in another field for a few years now homestead was just not working on my windows machine anymore and never having used Docker before you were my little lifeline here thanks for a very well explained step by step here was very helpful.
Only minor thing I had to do was the alias was nice to have however after shutting down and starting up again I had the set the alias again so ended up going into ~/.bashrc and manuelly adding it that seems to have fixed it for me
Thanks for sharing!
That's interesting. Haven't run into that. Thanks for posting for future watchers.
This was a fantastic guide, thanks for this and all your WSL content.
Hours of struggling with php version. Didn't know had to prepend sail. Thanks
So happy it helped.
You help a lot WSL users
Happy folks are finding it useful. Thanks for watching.
Thanks for this video!
You're welcome. Thanks for watching.
Hi, how can I run via PHPStorm terminal symbolic link folder on Ubuntu and open files in PHPStorm with the possibility of running the sail command in the terminal after?
(wsl2) ~/Projects > (windows) ~/Projects
Thanks this is reallly helpful, what if wanted to use postgres rather than MySQL how it can be configured?
Glad you found it helpful. You can likely change the DB preference in the Dockerfile.
thanks a lot
You are most welcome
I use wsl2 run docker-compose but still slow more then linux distro. I decided back to linux
Depending on the project, and the amount of data shared between the container(or VM) and host, I agree it can be too slow. And it also depends on how many times I need to refresh the browser, while developing.
the worst tutorial ever, saying you have 2 projects already in folder is not what we expect, do everything from scratch, and create them in video on the fly
I'm sorry that approach confused you. Having them pre-installed cut the video by 10 boring minutes. I was attempting to show the difference between Laravel apps with and without Sail installed, and I showed how to install Sail when not already installed. I hope that helps. Good luck with your learning.
I have been struggling to get docker and laravel working as well as understand everything. Even though some think this video is not detail enough there were enough things said that helped me out and was able to make more sense of everything. At the end of the day I was able to create a project and get docker up and running and the website responds in my local browser. Thanks.
Not the worst tutorial ever, but not very helpful for those of us who need to install Laravel Sail into an existing project. How did you possibly get Laravel Sail installed into your existing project? It requires you to have both PHP and COMPOSER installed in WSL2. That's an important thing to cover. Also, it requires all the PHP extensions that Laravel requires because COMPOSER will fail to install Sail unless all the extensions are present. If I'm going to have to to make WSL2 (Ubuntu) a complete Laravel development environment just to get to the point where I can install Sail, what is the point of Laravel Sail?