void 🌖
@leloup.dev
Adrien Leloup
I like code, food, and when people help each other.
Tech director @whitecube.be
Building @hiker.dev
Organizing @phpxbru.com 🇧🇪
I like code, food, and when people help each other.
Tech director @whitecube.be
Building @hiker.dev
Organizing @phpxbru.com 🇧🇪
I will say what we do is migrate the DB before running the tests, seed some data, then export to a SQL file that we can quickly re-import on a test by test basis. That's because we're running Dusk tests and so we can't use the RefreshDatabase trait.
November 12, 2025 at 11:33 AM
I will say what we do is migrate the DB before running the tests, seed some data, then export to a SQL file that we can quickly re-import on a test by test basis. That's because we're running Dusk tests and so we can't use the RefreshDatabase trait.
Another idea is to see if you need to run all the migrations for all the databases for every test or not. Maybe there's a way to structure your parallel execution so that you don't need every database to be migrated in every case?
November 12, 2025 at 11:26 AM
Another idea is to see if you need to run all the migrations for all the databases for every test or not. Maybe there's a way to structure your parallel execution so that you don't need every database to be migrated in every case?
I don't have anything quite that large but with 95 tables and 160 migrations, running the migrations is pretty quick and hasn't been a problem here. How long does it take to generate for you?
November 12, 2025 at 11:22 AM
I don't have anything quite that large but with 95 tables and 160 migrations, running the migrations is pretty quick and hasn't been a problem here. How long does it take to generate for you?
I don't think there's an obvious solution for that other than trying to see if there's stuff you can remove (changes that are introduced in a migration only to be undone by another migration down the line).
Maybe artisan schema:dump if you're not already doing it.
Maybe artisan schema:dump if you're not already doing it.
November 12, 2025 at 11:14 AM
I don't think there's an obvious solution for that other than trying to see if there's stuff you can remove (changes that are introduced in a migration only to be undone by another migration down the line).
Maybe artisan schema:dump if you're not already doing it.
Maybe artisan schema:dump if you're not already doing it.
> Ignition returns as open source...with the same rich debugging context we collect for Performance Monitoring.
Love to read this!
Love to read this!
November 12, 2025 at 10:45 AM
> Ignition returns as open source...with the same rich debugging context we collect for Performance Monitoring.
Love to read this!
Love to read this!
Dude I've been fighting the urge for the past few weeks as well! You got some stuff cooking already?
October 9, 2025 at 8:15 AM
Dude I've been fighting the urge for the past few weeks as well! You got some stuff cooking already?
Looks amazing, I admit I am a bit jealous of all the food you get to try with all the travelling you’re doing 😅
September 28, 2025 at 3:42 PM
Looks amazing, I admit I am a bit jealous of all the food you get to try with all the travelling you’re doing 😅
It's about @hiker.dev and how it was born out of our need to create an ERP with Laravel!
a squirrel is standing in front of a chalkboard with math equations on it
ALT: a squirrel is standing in front of a chalkboard with math equations on it
media.tenor.com
September 22, 2025 at 2:05 PM
It's about @hiker.dev and how it was born out of our need to create an ERP with Laravel!
That's a really great article, thanks for sharing :)
September 17, 2025 at 8:36 AM
That's a really great article, thanks for sharing :)