The Ease of Deployment Tier List for Laravel Developers

If you've spent any time in the front-end world before moving into the full-stack space, you quickly realize that deploying your application isn't as simple as just "connecting your GitHub account".

This is my personal tier list (opinions are my own, not sponsored) for what services just work when it comes to getting a Laravel app on the web, and what is much more trouble than it's worth. Let's check it out.

p.s. if you know Docker, then everything gets easier and moves up a tier, but I'm not that smart.

Help me choose my next video:

Links:

00:00 Intro
01:02 Laravel Deploy
02:07 Bootcamp Example
02:42 Deploy Options
03:20 Laravel Options
04:48 Vapor Benefits
05:53 Forge Benefits
07:16 Server Options
08:14 Pricing Info
08:37 Server Tiers
09:39 AWS Complexity
10:47 Third Party Options
12:06 Managed Services
13:28 Render Overview
14:21 Railway Overview
15:13 Flight Control
16:43 Fly IO Benefits
18:42 Fly IO Ease
19:49 Monitoring
20:30 Conclusion

for the algo:
Laravel deployment, Laravel hosting options, Deploying Laravel apps, Laravel server setup, Laravel background jobs, Laravel queues, Laravel production deployment, Laravel cloud hosting, Laravel Forge, Laravel Vapor, Laravel Envoyer, Laravel Valet, Laravel and Docker, Laravel tier list, Laravel on serverless, fly dot io, aws Laravel, Laravel easy deploy, Laravel Ploi

Keep creating.

---

[pythonantole]

I appreciate your pragmatic approach to web development, embracing it as a typical developer. In our industry, there's a common tendency for everyone to claim expertise, and there's a misconception that complexity equates to superiority. I've personally experienced judgment from 'senior' developers for using a Git GUI client instead of the command line, so I can relate to this challenge. Ultimately, prioritizing tools that enhance coding efficiency and faster delivery is far more valuable than adhering to norms that might create unnecessary friction based on outdated perceptions of how 'real developers' operate.

[abdu]

I really love your channel, also js developer swicthed to Laravel. I'd appreciate if you'd put more content around these js developer transitioning like us, topics like PHP Crash course, Laravel Livewire serious, Creating Composer CLIs, Laravel project folder strucure and OOP, and more. Thanks bro.

[razvangrigore]

I really appreciate your content, but as a devops and ex php developer, I would say learning Docker and taking the time to understand where and HOW your app runs, is as important as knowing how to write it. All those SaaS hide complexity away from you and on scale debugging becomes a nightmare. Not to mention vendor-lockin. A docker image is vendor agnostic, can be deployed everywhere and you got to tune it as a developer. Cheers.

[bebel]

I have been searching for a sail-like docker-compose but for deployment.
I mean, if sails can generate a docker-compose for us to work with Laravel locally, wouldn;t it be cool to have the same but for deployment? Like sails but with nginx/php-fpm instead of the php dev server...

Right now, I just generate my sail project, copy all the docker-related stuff, then I add nginx/php-fpm on top of it.
To make things even easier (but less performant), I store my cache, files and Scout servers all on the DB (using Mariadb).
So one DB, one HTTP server and that's it.

So, did you ever stumble upon something like sails but for prod?

[JamesJosephFinn]

What are your thoughts on the objection to Laravel which I've stumbled across that its release cycle introduces breaking changes every 12 months (which apparently used to be every 6 months—that must've been fun). "Breaking", i.e., lacking backward compatibility / inability to access new features from old code. Presumably one could theoretically continue to run the deprecated version; but it begs the question for how long that deprecated version would continue to receive support enough to be stable in production. Or is this just a reality of web frameworks in general; i.e. that one must be committed to rewriting / refactoring code on an annual basis? If I'm grokking this correctly, it seems to me that Laravel wouldn't be much different (in this regard) than the maintenance nightmare that has become the JS ecosystem. I value your insights. Peace.

[JonBrookes]

Fascinating insight into options out there for low friction deployment. I am intrigued by Bref and will subsequently look more into this - the idea of a Laravel app hosted as if twere a function and charged for when it is used and not for when it is not. Seems too good to be true but certainly worth the time to try it out. Thanks for all the tips, this is great.

I would recommend to anyone learning Docker at least if not containers in general and how to use these in a development life cycle. This leads into production delivery and as such is a good introduction to production concerns. It is like an 'interface' if you would to making your apps service ready and having consistent, repeatable and reliable environments from dev => prod.

I suppose I would say that, having learnt and used Linux since before y2k when it was slackware and on 20+ floppies but I'm on old curmudgeon i suppose. Ha ha !

[ripplesr]

The worst is the color theory of this ranking. D as green and S as red-ish. lol. Messed up. Thanks for the vdo though. Got a good look at the options I have for my project.

[Stoney_Eagle]

Oh hi, guess you're in the bucket of other twitch streamers I am subscribed to 😊