Multi-tenancy / multi-install

[ngm]

For situations where other organisations want to use the Fixometer, but in a way such that it more customised to their organisation. (In contrast to simply adding a new Group to our current install of the Fixometer.)

Outlining here some loose approaches to this. No need to go too deep now, until we have a clearer picture of which organisations might use the software and how.

Install Type

• multi-tenancy: SaaS-style where we host and maintain, but at login users are served the custom version of the site based on which organisation they are a member of
• multi-install: the software can be self-hosted

As a loose analogy, it's kind of wordpress.com / wordpress.org style options.

The type of install is mostly an operations issue. The architecture/implementation of variability is still needed regardless of install type.

Variability

Some key questions:

• What level of application variability is required (i.e. how much customisation/bespokeness needed)
• Data variability - this relates to the Open Repair Data Standard. We ensure important data collected is interoperable, but allowing for flexibility.

Example variability points that have already come up:

• when does the repair take place? (e.g. at an event vs during a working day vs ad-hoc repairs)
• external systems to be updated when some entity (e.g. event) is updated in Fixometer (e.g. Wordpress site vs external corporate system)

[ngm]

Types of organisations we may partner with:

1) commercial repair businesses 2) other networks of community repair 3) local authorities 4) associations /trade bodies