ENDOC-676 MT intro and top-level informational page with links #693
Conversation
There was a problem hiding this comment.
We'll need to update this diagram before publishing since it includes sme.com in the URLs. We'll need to make it generic.
There was a problem hiding this comment.
@nshaw what replacement urls should be used?
There was a problem hiding this comment.
@Lyd1aCla1r3 something like "mydomain.com", "tenant1.mydomain.com", "tenant2.mydomain.com" would match language we've used elsewhere. That makes it look like we only support subdomains but it is the most common use case.
There was a problem hiding this comment.
@Lyd1aCla1r3 something like "mydomain.com", "tenant1.mydomain.com", "tenant2.mydomain.com" would match language we've used elsewhere. That makes it look like we only support subdomains but it is the most common use case.
|
|
||
|  | ||
|
|
||
| Entando Multitenancy requires a tenant to configure Solr, Entando CDS, and Keycloak per the linked tutorials **TODO - Solr/CDS/Keycloak in this sentence will link to those**. | ||
| Entando Multitenancy requires each tenant to configure Solr, Entando CDS, and Keycloak per the linked tutorials **TODO - Solr/CDS/Keycloak in this sentence will link to those**. |
There was a problem hiding this comment.
can be addressed later but may want to add here that the Primary needs to be configured for Redis, Solr, and CDS and then the tenant work mentioned here
There was a problem hiding this comment.
to avoid implications wrt sequence and process i'll reword to the end result
|
|
||
| Multitenancy describes an architecture in which a single software instance serves multiple tenants. Each tenant, identified by a unique domain name, comprises a user group with specific access privileges to the instance. A multitenant software application is designed to provide a common architecture while ensuring the segregation of information. | ||
|
|
||
| Entando Multitenancy imposes a shared architecture (e.g. the versions of Entando, K8s and Keycloak) while distributing resources (e.g. CPU, memory) across the primary and secondary tenants. The primary tenant refers to the user group with full access to the default features and functionalities of an Entando instance. Secondary tenants comprise user groups who share certain privileges and capabilities of the primary tenant. |
There was a problem hiding this comment.
there should be commas after e.g.,
| A single installation of Entando can manage more than one independent and isolated site. While secondary tenant sites are dynamic and content-driven, their composability is limited. The following are key concepts of Entando Multitenancy: | ||
|
|
||
| - The domain name in the URL of the Entando instance identifies the current tenant | ||
| - Separate databases (or schema) and filesystems physically isolate each tenant's data |
There was a problem hiding this comment.
to follow the pattern of plurals (or schemas)
TODOs awaiting tech installation/configuration guides