Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is seeds supported? #9

Closed
andheiberg opened this issue Jul 21, 2014 · 4 comments
Closed

Is seeds supported? #9

andheiberg opened this issue Jul 21, 2014 · 4 comments
Labels

Comments

@andheiberg
Copy link

Hi there,

Is there a strategy for seeding the databases?

@crynobone
Copy link
Member

Not at the moment, but I'm open for PR on this 👍

@andheiberg
Copy link
Author

Well I've already built a different setup for this and my usage isn't really covered by this package.

I'm just curious.

What is your use case for this package?

@crynobone
Copy link
Member

What is your use case for this package?

I building a multi-tenant but using shared database (some call it Shared Tenancy). As an example a CMS setup where the user/permission are shared while posts, comments etc (related to CMS) is separated per domain.

The code is now improve to support Application Tenancy where each tenant could have it's own database connection. However the main different is that this package doesn't use any Artisan::call() from a web interface which I would consider as a hackish approach.

@andheiberg
Copy link
Author

It's difficult for me to express why I can't use this simply. But basically it comes down to the fact that my User/Permissions and CMS is in different applications, so my strategy for tenancy is different I guess.

But this looks really cool though :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants