tenancy VS laravel-modules

https://tenancyforlaravel.com/ have a look at this - looks like you’re going to need a wildcard ssl to get this to work - but this package was very helpful. And looks like it could cut out a lot of the work for you.

That's a bit confusing, too, to have a page that was working suddenly fail on a refresh. For multi-account admins, I tend to prefer an approach that puts the company in the URL, like /admin/{company}/foo or a subdomain-based approach. Both tend to be supported by systems like https://tenancyforlaravel.com/.

Use this https://tenancyforlaravel.com/

I do not consider it a reasonable request. The burden to maintain an open-source project is already heavy and entitled users should be flagged whenever possible.

Examples abound. Came across this one recently: https://github.com/archtechx/tenancy/issues/654#issuecomment...

If you need the data from each Company to be completely isolated (for security reasons, with zero chance to access another company’s data), then you’ll have to use multi tenancy. Check this package or similar: https://tenancyforlaravel.com/

We use this package: https://tenancyforlaravel.com/ , but there are others including one by Spatie. There are similar libs for just about every framework in every language.

have u ever heard about Tenancy for Laravel ? Personally I have never use this but I might have a little understanding about your struggle here. So imagine "The Organization" is a Tenant, and each Tenant can have a sub-Tenant and so on, this package (AFIK) only cover the first-layer of tenants and I think you can extend the code of package so each tenant may have a sub-Tenant (nested). CMIIW.

I am building a multi-tenant SaaS application using this tenancy package from Tenacy for Laravel. It has a concept of tenancy bootstrappers that modifies relevant framework defaults to make the application tenant aware. The FileSystem Bootstrapper makes the Laravel asset() helper method return tenant specific assets through a TenantAssetController. I also replaced Laravel Mix with Vite and I'm using this Laravel Vite package to make the integration easier. The package provides @vite directive to output all the necessary asset tags in your blade file. The underlying methods use the asset() helper method from the framework. Therefore, any generated asset URL is tenant-scope if I am under a tenant aware route. I am using VueJS for templating so my page ends up not being rendered correctly.

If you check their GitHub for how this command is implemented you can see how they access the Tenant model. You might be able use this for your own command: https://github.com/archtechx/tenancy/blob/3.x/src/Commands/TenantList.php

Oh you mean Domain Driven Design, you can do that in Laravel. I worked on plenty of projects who did it like that. You can even find packages for that, like this one https://github.com/nWidart/laravel-modules.

I recommend using this package https://github.com/nWidart/laravel-modules makes building with modules easier.

We recently changed our repository with using https://github.com/nwidart/laravel-modules

There are a bunch of options, we started with Domain Driven Design which I like since it organizes things while still allowing for core laravel. But you need to answer some questions first like will you support/handle multi tenancy? if so, how? Do you want features like Single Sign On? And so on. No need to answer me, thats for you to answer yourself as it may impact your layout decisions. After doing some work with the Laravel modules package from nWidart (https://github.com/nWidart/laravel-modules), there are some things I really like in there as well, which I kind of wish I had used that first. We're too long in the tooth so to speak to migrate over, and I haven't answer all my questions for that, such as how that handles vue.js, it seems very blade centric and we don't use blade at all in our app. But having a Modules folder with all of the bits from controllers, models, views, etc contained is very nice. In your case I would do some research on those things and what others here have suggested. One of the hardest things no one talks about is maintaining a large app as it grows in scope and creep. Implementing strong organization up front can be a huge help.

I totally agree with this, but I’d like to mention an exception. I found using nWidart’s laravel-modules library highly useful as a utility for creating and interacting with individual modules, as well as the ability to customise the stubs that generates them.

i'm trying to edit an existing application which it's using this package and what i want is to add the SaaS module for this application and also have a dynamic subdomain that depends on the company that want to buy this product..;

For a typical Laravel application, you could leverage namespaces, service providers, autoloaders, packages, API routes to totally separate these modules. There is a package that could help with this. Check it out here: nwidart/laravel-modules.

If you find your project is getting truly large, you could always explore breaking the entire codebase into modules: https://github.com/nWidart/laravel-modules