In a project of mine, i'm using a the tenancyforlaravel library.
This library work by overriding paths for a specific tenant. (database, cache, queue and of course storage)
can we update your logic (small changes) to leverage the internal disk implementation ? This would keep the indexes per separated for each tenant.
I can obviously do the pr if you give me your approval
thanks in advance for taking the time to read this and, of course, for the wonderful library
Hi,
In a project of mine, i'm using a the tenancyforlaravel library. This library work by overriding paths for a specific tenant. (database, cache, queue and of course storage) can we update your logic (small changes) to leverage the internal disk implementation ? This would keep the indexes per separated for each tenant.
I can obviously do the pr if you give me your approval
thanks in advance for taking the time to read this and, of course, for the wonderful library