How YOU Deploy Laravel Projects? Survey Results.

I conducted a short survey, and let's discuss the numbers and opinions from 447 respondents.

00:00 Intro: About Survey
01:31 TOP Server Providers
02:05 WHY Shared Hosting?
07:52 Deploying on VPS
08:34 TOP Tools You Use
09:05 How Laravel Forge Works
10:27 Deployer / Envoyer / Ploi
11:10 CI/CD Tools
11:53 LOLs and Emotions :)

My older videos about Laravel Forge:

- - - - -
Support the channel by checking out our products:

[nobnobnobnob]

This video is Gold. This is how should a community work. Thank you for this.

[mikevwoods]

Thanks so much. Fantastic video as all of yours are. I'm a retired IT guy doing Laravel as a hobby really. Fascinating to compare my journey with your gang!

[abdmaster]

Thank you for making this video. This is showing the current real world seanario. Speacially the shared hosting stuffs. Not all companies or person can afford vps ones or sometimes can't even get the privilege to purchase. In my country it is hard to get international items to purchase.

Hope this will help others.
Thanks again.

[Thotsuya]

Clearly one of the best explanations on the topic. I think that, specially for juniors it is a headache when you start deploying your project, as there are many ways to do so. I'm personally moving from Shared Hosting to DigitalOcean, to avoid headaches from setting a laravel project on a Shared Hosting

[Umarwaqas]

I was thinking i am the only one who use zip and unzip, but great to know all, you are really doing a great job 👍

[stygis]

Would like so see more info for advanced users. Like proper CI/CD, how to tests things before production and so on...

[coolcha]

Thanks for this video. I use Google App Engine (serverless) Standard with Google Cloud SQL for laravel. It is very simple to setup, scale and deploy. I am surprised this is not used as often.

[geeksy]

Hey very nice to see. On note here: I am working in market research (yes, powered by laravel :)) and I would recommend, for any upcoming surveys, to use options instead of open answers. Not only is it easier for you to gather the answers, but it will also result in a much higher participation rate. Just my 2 cents and thank you for your work. My team learned a lot from your channel!

[simonsdigital]

We primarily use Jenkins to pull, build, test via docker etc then SCP artifacts to destination (mainly for removing link to git on application servers), rebuild and symlink live. A nice way of ensuring we never mutate or destroy old deployments. There was a great tutorial done during a past laracon on using Jenkins with laravel for anyone wanting to learn more

[JacquesvanWyk]

I have been using Ploi for last few months and very happy with it

[NjoguAmos]

Been using Ploi and am happy with what they have to offer.

[HendraSusanto]

I use PHPloy to deploy the changes. Although it is manual, the good thing is it only deploys changes based on files changed in commit files in Git, so I don't need to deploy the whole app or remember which files are changed and should be deployed.

So if the deployed version in your server is on commit 1 while your local is on commit 3, it will only deploy changes in commit 2 and 3.

What's good about this is, if it's really really necessary, you can basically log in to your production server and change stuff quickly (for example to fix a very simple but very bad typo or some critical bugs) rather than having to go through the whole "make changes, git add, git commit, merge to master branch, then phploy" process.

I once tried both the manually git push from local then git pull from live (or setup an automated git hooks), but when I tried to do a production change above, it ends up making the repo in the production server having a staged git changes, making the future git pulls fail because there is an ongoing change not yet committed. I could manually git add then push in production then pull the changes to my local, but it ends up being a hassle.

Haven't really explored the envoyer (deploy to a release folder, then symlink the live version to that release folder) thing, because it seems to require quite a major change (since it requires storage and upload folders to be tweaked to survive changes between releases) and if the changes to be deployed is only a fix on typo in one file, it seems a bit overkill to deploy a whole release containing the whole app? I get that the advantages is we can roll back to previous releases quickly, but I find it easier to fix the breaking bugs quickly then deploying the necessary updates in the near future.

Of course this method works because I work in a quite a small team (< 5 developers), I'm sure it doesn't scale in bigger teams with more complicated deployment processes.

[imamhsn]

Thanks you very much Sir... I used to use ssh on shared hosting.

[odehadejoh]

Finally, someone agrees with me on Laravel Forge's Automatic Deployment is rather risky for a production server. Personally, I've never used it. Always have my Forge open in a browser tab. Doesn't take me 5 seconds to push deploy. I'd just rather not have some code I merged but haven't tested, go up to the live server.

[abdulbasitsalah]

the whole yesterday i was thinking and searching how to deeply laravel

thanks man 😍

[hollyhayes]

Thanks for this interesting video. I use Laravel Vapor and was surprised it didn't come up more. I hate server administration stuff and find Git a little difficult, and I like the auto-scaling, so this was a great option for me. I will have to see how the costs are in the long run, though, and whether it's the best option for all my sites.

[learnwithzeem]

PPT was well formatted n thanks to explain us 💯💯💯

[mounirammi]

One killer option for me on the shared Hosting, I just learned that Laravel's/Filament database notifications doesn't work on Shared Hosting, only on VPS. To just test the functionnaloity, you need to queue:listen command in the terminal and stay there. So it's a killer function that shared hosting doesn't have.

[mokhosh]

Tip for the next survey.
Use more checkboxes, radio buttons and select boxes, and less textareas. It will definitely help with summarising and visualising the data.

[rajaasyraf]

Great content! Very useful insight. Thanks for sharing this. :)