Federation server is mifos installation local
Status | Decided |
|---|---|
Stakeholders | @Markus Geiss (Deactivated) @Myrle Krantz (Deactivated) @Ed Cable @Craig Chelius |
Outcome | Customer deployment. We may later decide to provide a central deployment as well, the use of which would be optional to the customers. But our first implementation will be a customer deployment. |
Due date | Dec 11, 2015 |
Owner | @Myrle Krantz (Deactivated) |
Background
We have two choices:
A global deployment hosted by us
We would setup one uber federation server hosted at mifos.org
Every customer would need to add an entry with the following details: company and tenant (e.g. conflux, novopay)
The mapped address would look like this: conflux-novopay*mifos.org
A per deployment hosting by our customers
Every customer would setup its own federation server hosted at their domain (e.g. confluxtechnologies.com)
Every customer would need to add an entry with the tenant name
The mapped address would look like this: novopay*confluxtechnologies.com
Both solution have its pros and cons:
Would make the deployment very easy, but forces our customers to store some (maybe nondisclosure) information at Mifos.
Would need a deployment at the customer site (we'd need to provide a How to guide), needing to connect this component to the internet.