- Flask or Phoenix (Phoenix Live View if websockets are very important)
- Amazon Dynamo for (DB)
- Elastic Beanstalk
11–20 of 45 posts
- Flask or Phoenix (Phoenix Live View if websockets are very important)
- Amazon Dynamo for (DB)
- Elastic Beanstalk
No cloud vendor lock-in. Small image sizes. Easy on-boarding. Simple and productive.
Earlier quoted context omitted.
You could self host as it's all open source, but that would be a lot more work.. Reliability, it depends on your app and requirements. Been using them for about a year and it has been really solid, the few times I did have some issues the support was really quick and helpful. But I do see your point, it might not work for everyone.
Self-hosting Supabase is pretty hard when you consider mail set up, and all the config like setting your own domain/secrets/config without the full dashboard Supabase managed service provides, doesn't it? Aka you can't just get-up-and-go fill in a nice UI/form on an EC2 instance AMI template for Supabase...
I still find it important that the option exists if ever needed, and maybe even more important is the ability to move away from Supabase, which some people have done successfully (see for example https://news.ycombinator.com/item?id=36004925)
Other services like Firebase make that really complicated. I quite like that portability is one of their core principles.
There are some guides and templates on self hosting https://supabase.com/docs/guides/self-hosting but it's obviously a big complicated project with lots of features. It probably also requires a bunch of work to monitor, maintain and update it once you get it running.
I would use Laravel
1) Auth
You can create your Laravel app choosing (Vue + Inertia) or (Livewire) and have auth, 2FA and a profile dashboard in a few minutes, with Laravel Socialite package you can quickly add single sign on with Google Auth, GitHub, Octa, dozens of options. Oauth with Laravel Passport.
2) Simple user dashboard with live updates. I prefer Livewire or you can use View + Inertia these would have been installed in the previous step. You can also use Laravel Nova, or Filament to speed things along building a dashboard.
3) Blog I would run this standalone from the app and use Statamic, Next js or just html + tailwind css depending on the complexity
Laravel Ecosystem
Herd - macOS app that makes setting up your local dev environment instant.
Jetstream - Start a new project with auth and team management.
Telescope - debugging and insight UI
Scout - Lightening fast full text search
Echo - WebSockets
Cashier - Stripe and Paddle Subscriptions
Envoyer - Zero Down Time Deployments
Forge - Server creation and management (EC2)
Vapor - Serverless Creation and management
Horizon - Redis Queue Monitoring
Pennant - feature flags
Sail - Local Docker
Socialite - Social Auth Google, Facebook, GitHub (tons of drivers)
Sanctum - API and mobile auth
Pint - Code style fixer
Dusk - Automated browser testing
Inertia - SPA with server side routing
Livewire - Dynamic server side apps. (Similar to Rails/Hotwire)
And those are just some of the first party packages and tools.
There are well maintained Laravel packages for almost everything else you need.
And working with Laravel is the best developer experience.
Use what you know, what you are efficient with, what you like to use. I would use Laravel 1) Auth You can create your Laravel app choosing (Vue + Inertia) or (Livewire) and have auth, 2FA and a profile dashboard in a few minutes, with Laravel Socialite package you can quickly add single sign on with Google Auth, GitHub, Octa, dozens of options. Oauth with Laravel Passport. 2) Simple user dashboard with live updates.…
I love Svelte for client side stuff but in truth 80-90% of UIs can be solved with HTML over the wire.
Personally I'd choose the LAMP stack because it's what I'm most familiar with for web development and I know I can rapidly build a performant functional product with it, but for you that might be something else.
I haven't used it yet, but for my next full stack project I want to try Laravel with Livewire. I love Svelte for client side stuff but in truth 80-90% of UIs can be solved with HTML over the wire.
One recent raise that I was talking a new entrepreneur through had the investor take a hard pass as soon as they found out he was building with Laravel.
This isn’t the first time but in the past it was suspicion and wasn’t so explicit. They literally passed on giving a term sheet specifically because they were built in laravel… so I finally got someone “on the record.”
I have built startups with PHP and had great success, though I use a lot of platforms now and not as much php anymore, but I wonder if there is any issue with the raise.
I know the technicals (and how dumb it was, the first version gets trashed always anyways) but I wonder if others have seen this?