- 🇺🇸United States m.stenta
There hasn't been activity on this, so I'm going to close it as "won't fix" for now. It seems like this shouldn't be farmOS core's responsibility. It keeps things simple for core to just consider itself a "single farm". That said, I think everything that would be necessary for this could be implemented in an add-on contrib module. Experimentation can happen there, and if something solid and stable comes out of that and we want to reconsider adopting it into core, we can reassess at that time.
For what it's worth, I made a proof of concept module here (NOT FOR REAL USE): github.com/mstenta/farm_multifarm/
- 🇺🇸United States m.stenta
Relevant update: farmOS core will be adding a concept of "Organization" entities with a "Farm" sub-type by default.
Here is the pull request that is currently being worked on: https://github.com/farmOS/farmOS/pull/849
This ONLY adds a concept of "Farm Organizations" and allows assets to be linked to them. It does not add any access restrictions or automatic filtering of records by farm. That is still where the bulk of the work lies in implementing a "multi-tenant" instance of farmOS.