I dealt with this real bad for almost two years about a year and a half back. Used talonvoice.com aggressively and have recovered pretty well, not 100% but I haven't had to use the voice controls to feel okay for a while.
If you started the project recently it would likely have created a SQLite database file for you when running the migration, although I suspect Copilot wasn't thinking about that even if it would've worked 😂
I've used both even in the same project. Terraform to manage the servers, Ansible to manage the application.
I imagine they'll do new account promos, use it for credit, stuff like that. That tends to be the use case for such a system. I wouldn't expect to get enough of a discount there to make it financially viable if it's not already viable for you.
Are you talking about the invoice page that will show a couple of things, including discounts?
I don't think there are any public discounts at the moment.
What kind of experience are you trying to create? Breeze is one you install but it boils down to placing stubs into your resource and app directories, and wouldn't be too hard to copy/tweak.
Most alternative starter kits I've seen are GitHub templates that you copy.
I just tried to set this up last night but following the Inertia docs didn't get me a working setup, and I couldn't find an article talking about it. Any tips for actually getting this stack up and running? 😅
I'm not sure how if it's not installed, but I thought it checks APP_DEBUG, not APP_ENV
Laravel VS Code extension ships Monday in public beta. ✨
Have you played around with ingesting data from the firehose? I'd build two things, something extremely performant for handling the ingest, and then I could see Laravel being used on the user facing side when someone wants to load their feed.
I don't think using PHP for ingestion would be the best.
I assume they mean a feed generator that lets you create a feed people can subscribe to such as the Discover feed.
It's unfortunately not trivial. You have to ingest every event that happens and filter down to just what you want.
Good luck 🫡😂
Coding one isn't even the hardest part. Just ingesting the amount of activity that comes through the firehose is hard, and that's not even taking into account requests to load the feed which ping constantly for everyone that's viewing it.
I was messing with it and almost needed Kafka for the demo 💀
Then you're in luck! It sounds like they're going to replace the starter kit packages with GitHub repos you can clone (like how laravel/laravel is today)
bsky.app/profile/tayl...
The Breeze starter kit has a TypeScript option. I thought Jetstream did as well but I guess it doesn't.
For sure, although Herd can also manage many of those services as well now 🙂 Just depends if I feel like spinning up/down Docker for a project or if it'd be nice to just have it running natively when I need to work on it.
I like Docker for projects with multiple devs or if the deployment target will be containers, but for a lot of stuff I'm the only one working on it, and it's going to be deployed on a basic server, so running it locally with Herd is pretty close to the real environment and makes it easy to manage.
This does look pretty slick, thanks for sharing!
More open to introducing a vulnerability, for sure. If you validate and only use validated request values then you won't be vulnerable.
If you like to pass `$request->all()` to your models, then definitely don't do this 😅
That being said, I like to use fillable and strict validation lol
Does Deno have a framework comparable to Rails/Laravel?
project-name.test (w/ SSL thanks to Herd) ✨
Breeze is lightweight auth + basic account settings. Jetstream has more advanced account settings and also a team option (although it's not my fave implementation).
If you're asking because you're learning Laravel, use Breeze 🙂
Just saw this in the recent Laravel update video, nice!
Yeah, that's what I mean. You can't use it without paying for it, right? Wouldn't make much sense to let it be put into a public repo.
Isn't Flux a proprietary library?
Oh wow, I've never seen that before. www.php.net/manual/en/fu...
I'll have to test this out and see what differs from `Class::staticFunction` which I don't use ever but is what I would've assumed does what the first class callable seems to do.
* function name, not functional.
That being said, you could totally call a static function if you wanted to.
of controller functions not being static is that you can have a constructor in your controller that can automatically resolve dependencies bound in the container, like services that require a lot of setup or config values, etc.
Passing the controller and functional name allows for all of that.
Controller functions don't have to be static. The default functions when you generate a controller using Artisan are not static.
If you called static functions, you couldn't have route model bindings and dependency injection. You could pass a reference to the controller function, but the benefit...
I could see the argument that they are two separate notifications and thus shouldn't be located in the same Notification class, but my personal philosophy is to use things like custom helpers as infrequently as possible because new users (or future self who's forgotten) have to relearn how it works.
