Upgrading Laravel Framework within same major version e.g. 8.xx

  If you came for quick answer: composer update To understand why we do this, let's explore a bit in the composer.json file. You will see something like this:           "require": { ... "laravel/framework": "^8.12", ... } We're done. Just be mindful you're also updating a whole list of other dependencies.  You should be able to specify the version you want by changing the value to example: "require": { ... "laravel/framework": "8.32", ... } For major version upgrades from version 7.x to 8.x or any major releases, you may check the official documentation  here .  To find out what the latest versions are: have a look in its official Github page  here .  If you ever think of having this done automatically, I recommend to look into   Laravel Shift .

Why I use Laravel Forge

After 4 months using Laravel Forge , I only have positive experience. If you're wondering should you give it a try, I hope my attempt to write this post can give you some clarity.  It is convenient .  I needed to show a website to a prospective employer which I've developed using Laravel framework. Using forge helped me reduce the server configuration time, I was able to launch the site in a night.  You can look at it as your deployment server manager with a clean UI. If you're not familiar with any of the deployment terms, you may want to check Git and GUI Clients to understand better.  You would still need to choose your choice of cloud infrastructure provider such as  DigitalOcean and AWS  which have their own billing cycle. Laravel Forge provides an easy way to connect your Forge account to your cloud provider account.  You can also enable auto-deployment in Forge which I find useful. I like to be able to see any deployment errors from the Forge UI. To access your pr

Adding project folders into your Homestead

If you create a Laravel project in homestead, you will notice that the project folder in your local machine is empty - while the newly created Laravel app is up and running. This might very well due to your mapping in `homestead.yaml` file isn't correct.  Let's elaborate more, if you use Laravel homestead, to create a project using the command: laravel new AppName We run the command above in the vbox machine as guest machine. This will create a folder `AppName` in your guest machine. The app is working. You may think that mapping this way will do the work assuming you already have `project1` : #- map: ~/code/project2 # to: /home/vagrant/code/project2 You will see that your `project2` folder is empty in your local machine. To fix this, I'd suggest this approach - first create a new mapping path (a general path from the local machine's project directory to the vagrant's code directory / project directory whatever you use in vagrant). You can do this by updating yo