@andy thanks for your support, I'm really looking forward to feedback. At this time I'm finishing up on a preliminary version of the management interface, which will allow the demo on-site to work and shows the power of the multi tenancy packages.
Also started work on a way to allow for migrations to be run on system and tenant websites more easily.
working slowly towards a stable release, a lot of effort now goes into the travis build, the framework package now also contains unit tests and tests integration with laravel
My apologies on the silence the past week. I've been extremely busy on larachat.co (slack), discussing this way and that. Hyn multi tenancy never stalled though. Currently I'm revisiting the old pain of overruling the migrate command. My priorities are with that functionality which is highly blocking. Once done it guarantees a higher flexibility to use the package as you need. Also documentation will be required to explain the migrate extension.
A newsletter will also go out once I firmly believe the migrate command works stable for tenants.
After quite a heated discussion on a.o. slack we've moved away from the relation with thé php league, finding the definite namespace "Laraflock". The multi tenancy package will be maintained there, no namespace changes anymore. Further news will follow soon as the new management interface will be finished up.
The latest newsletter explains how to use the package as a developer and gives insight into the near future for this multi tenancy solution. See: http://createsend.com/t/i-DF339390B176E076
I saw the package on multi-tenant and I liked it. But my concern is around the multiple databases. I just need a single database for all the tenants since it is a single application (I have other reasons for considering that although). Is there any way to suite my need?
Hello @peter at this time my package does not support this. The base idea behind the package is the concept of SAAS, the requirement of being secure and unobtrusive. As such I am unsure whether sharing one database between tenants is a strategic direction I'm willing to move into with this. There are however alternatives I've listed in the readme of my project that do use a shared database.
On a general note my apologies for the silence here, I have been busy working on these packages, while supporting the open source community in other ways as well.
A new newsletter is around the corner, in which I discuss an automatic installer and a probable stable release.
This morning I've send out a newsletter announcing the release of beta 3, which includes an installer script, which allows the installation of a multi-tenant Laravel 5.1 with all requirements needed for proper functioning of the application.
Version 0.8.0+ has been announced in the latest newsletter. Version 1.0.0 is expected before 2016. The current version is not backward compatible due to a final namespace change to Hyn.
@peter I have been adding the functionality to separate tenant databases using prefix only (dev-master currently).
@larsn Hoped you would be able to tell me whether I have been able to stick to your requirement of keeping features to a bare minimum, it's something I value as well.
@samsoft@jartaudhyn/multi-tenant should now be stable enough for you to use in production environments; if you encounter issues please do let me know so I can assist in getting you along ASAP.
@gabrelbuzzi please let me know on github as issue if you encounter any problems installing this on Laravel 5.2. Make sure you use the 2.0.0-beta.3 version!
Version 3.x is upcoming, is a complete rewrite and is meant to be compatible with Laravel 5.3 and up. In addition it supports mariadb and postgresql, read more about it:
@cheetooh books? No; but you can take a look at the (slightly) outdated tutorial by @ashokgelal ; an updated version is in the makes by a community member: