The package I'm working on currently, called Seedling, whose primary function is to allow developers to provision databases (credentials, grants, etc) for their tenants, may be getting a rework (and new name). Provisioning tenants could require other services too.
Since Sprout sets context information about the current tenant, this will work out of the box with Sprout.
Nightwatch now allows you to add additional metadata to your events to make them easier to debug. Super simple to add information about a user's current plan, feature flags, and more. Just use Laravel's built in Context feature to get started. 🦹 nightwatch.laravel.com/docs/features/…
This will also include some minor tweaks to the logos and icons, as they're things I essentially threw together in a couple of hours. I'm currently experimenting with different options for the main icon. (I'm fond of the bottom one)
The plan is to launch an updated site along with v1 for the add-ons Bud, Seedling and Terra. At the same, the Laravel starter-kit Allotment and the dev-kit Propagator will be released. #laravel #multitenancy
I'm currently experimenting with Propagator, the dev-kit, including the option to have the Sprout config managed by the dev-kit. Rather than publish and modify, you use an interactive CLI command to update it, simplifying things. At least that's the hope.
So there's a @LaravelSprout package called Bud, that lets you have custom DB connections, broadcast connections, mailers, auth providers, etc, per tenant, driven by the database. I've been working on it, and have had to remind myself how it works 😂
I think I’ve just figured out how to do tenant-specific queues with Horizon too. Though, it’s going to require some sharding I’d imagine, splitting across multiple connections.
I'd also like to improve the Sprout website, so if anyone has suggestions, I'd love to hear them! #multitenancy #laravel
Good news. I've simplified it massively, and messages can now be broadcast only to clients connected under the same app as the message was sent. Isolation can be either channel or application level.
I'm fairly confident that I've just figured out how to have not only tenant-specific applications for Laravel Reverb, but also tenant-specific events. All tenants can subscribe to the same channel, but only see events scoped to them. I think. #laravel #multitenancy
While I'm talking about overriding stuff, I've also figured out Octane support, and I believe, I've figured out Nightwatch too. So you can have each tenant have their own Nightwatch credentials.
The video version of my article is now live! Multi-tenancy without the hassle in @laravelphp thanks to @LaravelSprout by @ollieread youtube.com/watch?v=jAuAAm…
youtube.com
YouTube
Effortless Multi-Tenancy in Laravel: No More Headaches with Sprout
There aren’t a lot of good options for multi-database with segregated resources, I’d be very interested in articles around that kind of enterprise level tenancy 👀
United States トレンド
- 1. Flacco 86.3K posts
- 2. Bengals 81.3K posts
- 3. Bengals 81.3K posts
- 4. Tomlin 22K posts
- 5. #clubironmouse 3,090 posts
- 6. Ramsey 19.3K posts
- 7. #criticalrolespoilers 8,210 posts
- 8. Chase 108K posts
- 9. Chase 108K posts
- 10. #WhoDidTheBody 1,615 posts
- 11. yeonjun 118K posts
- 12. #WhoDey 6,903 posts
- 13. #SEVENTEEN_NEW_IN_LA 45.4K posts
- 14. Cuomo 85.4K posts
- 15. Teryl Austin 2,819 posts
- 16. Andrew Berry 3,290 posts
- 17. Xenoverse 3 N/A
- 18. Tame Impala 5,627 posts
- 19. Max Scherzer 14.6K posts
- 20. Burrow 9,941 posts
Something went wrong.
Something went wrong.