docs: Merge tenant data model recipes into single page

Author: igorlukanin

docs/pages/product/configuration.mdx

@@ -16,8 +16,19 @@ to; changing that list would require the deployment to restart.
 
 </InfoBox>
 
+<ReferenceBox>
+
 See the [environment variables reference][link-env-vars] for all supported options.
 
+</ReferenceBox>
+
+<ReferenceBox>
+
+See [this recipe][ref-env-var-recipe] if you'd like to reference environment variables
+in code.
+
+</ReferenceBox>
+
 ### Cube Core
 
 You can set environment variables in any way [supported by
@@ -47,8 +58,13 @@ processed by Cube.
 </InfoBox>
 
 Configuration options take precedence over environment variables.
+
+<ReferenceBox>
+
 See the [configuration options reference][link-config] for all supported options.
 
+</ReferenceBox>
+
 ### `cube.py` and `cube.js` files
 
 Configuration options can be defined either using Python, in a `cube.py` file,
@@ -200,3 +216,4 @@ mode does the following:
 [ref-python]: /product/data-modeling/dynamic/jinja#python
 [ref-javascript]: /product/data-modeling/dynamic/javascript
 [ref-cube-package-config]: /product/data-modeling/reference/cube-package#config-object
+[ref-env-var-recipe]: /product/configuration/recipes/environment-variables

docs/pages/product/configuration/multitenancy.mdx

@@ -29,6 +29,14 @@ Token][ref-security].
 There are several multitenancy setup scenarios that can be achieved by using
 combinations of these configuration options.
 
+<ReferenceBox>
+
+See the following recipes:
+- If you'd like to provide a [custom data source][ref-per-tenant-data-source-recipe] for each tenant.
+- If you'd like to provide a [custom data model][ref-per-tenant-data-model-recipe] for each tenant.
+
+</ReferenceBox>
+
 ### Multitenancy vs Multiple Data Sources
 
 In cases where your Cube data model is spread across multiple different data
@@ -391,3 +399,5 @@ input.
 [ref-security]: /product/auth
 [ref-cube-datasource]: /product/data-modeling/reference/cube#data_source
 [ref-cube-security-ctx]: /product/data-modeling/reference/context-variables#compile_context
+[ref-per-tenant-data-source-recipe]: /product/configuration/recipes/multiple-sources-same-schema
+[ref-per-tenant-data-model-recipe]: /product/configuration/recipes/custom-data-model-per-tenant

docs/pages/product/configuration/recipes/_meta.js

@@ -1,8 +1,7 @@
 module.exports = {
   "environment-variables": "Environment variables",
-  "using-different-schemas-for-tenants": "Different data models for tenants",
-  "custom-data-model-per-tenant": "Custom data model for each tenant",
-  "multiple-sources-same-schema": "Multiple data sources",
-  "using-ssl-connections-to-data-source": "SSL with data sources",
-  "data-store-cost-saving-guide": "Data store cost saving guide"
+  "using-ssl-connections-to-data-source": "SSL",
+  "data-store-cost-saving-guide": "Data source usage",
+  "multiple-sources-same-schema": "Per-tenant data sources",
+  "custom-data-model-per-tenant": "Per-tenant data models"
 }

docs/pages/product/configuration/recipes/custom-data-model-per-tenant.mdx

@@ -348,6 +348,153 @@ module.exports = {
 
 </CodeTabs>
 
+#### Example
+
+Here's an example of how to use this approach. Let's say we have a folder structure
+as follows:
+
+```tree
+model/
+├── avocado/
+│   └── cubes
+│       └── Products.js
+└── mango/
+    └── cubes
+        └── Products.js
+```
+
+Let's configure Cube to use a specific data model path for each tenant using the
+`repositoryFactory` function along with `contextToAppId` and `scheduledRefreshContexts`:
+
+```javascript
+const { FileRepository } = require("@cubejs-backend/server-core");
+
+module.exports = {
+  contextToAppId: ({ securityContext }) =>
+    `CUBE_APP_${securityContext.tenant}`,
+
+  repositoryFactory: ({ securityContext }) =>
+    new FileRepository(`model/${securityContext.tenant}`),
+
+  scheduledRefreshContexts: () => [
+    { securityContext: { tenant: "avocado" } },
+    { securityContext: { tenant: "mango" } },
+  ],
+};
+```
+
+In this example, we'll filter products differently for each tenant. For the `avocado`
+tenant, we'll show products with odd `id` values, and for the `mango` tenant, we'll show
+products with even `id` values.
+
+This is the `products` cube for the `avocado` tenant:
+
+<CodeTabs>
+
+```yaml
+cubes:
+  - name: products
+    sql: >
+      SELECT * FROM public.Products WHERE MOD (id, 2) = 1
+```
+
+```javascript
+cube(`products`, {
+  sql: `SELECT *
+    FROM public.Products
+    WHERE MOD (id, 2) = 1`,
+
+  // ...
+});
+```
+
+</CodeTabs>
+
+This is the `products` cube for the `mango` tenant:
+
+<CodeTabs>
+
+```yaml
+cubes:
+  - name: products
+    sql: >
+      SELECT * FROM public.Products WHERE MOD (id, 2) = 0
+```
+
+```javascript
+cube(`products`, {
+  sql: `SELECT *
+    FROM public.Products
+    WHERE MOD (id, 2) = 0`,
+
+  // ...
+});
+```
+
+</CodeTabs>
+
+To fetch the products for different tenants, we send the same query but with different
+JWTs:
+
+```json
+{
+  "sub": "1234567890",
+  "tenant": "Avocado",
+  "iat": 1000000000,
+  "exp": 5000000000
+}
+```
+
+```json5
+{
+  sub: "1234567890",
+  tenant: "Mango",
+  iat: 1000000000,
+  exp: 5000000000,
+}
+```
+
+This approach produces different results for each tenant as expected:
+
+```json5
+// Avocado products
+[
+  {
+    "products.id": 1,
+    "products.name": "Generic Fresh Keyboard",
+  },
+  {
+    "products.id": 3,
+    "products.name": "Practical Wooden Keyboard",
+  },
+  {
+    "products.id": 5,
+    "products.name": "Handcrafted Rubber Chicken",
+  },
+]
+```
+
+```json5
+// Mango products:
+[
+  {
+    "products.id": 2,
+    "products.name": "Gorgeous Cotton Sausages",
+  },
+  {
+    "products.id": 4,
+    "products.name": "Handmade Wooden Soap",
+  },
+  {
+    "products.id": 6,
+    "products.name": "Handcrafted Plastic Chair",
+  },
+]
+```
+
+You can find a working example of this approach on [GitHub](https://github.com/cube-js/cube/tree/master/examples/recipes/using-different-schemas-for-tenants).
+Run it with the `docker-compose up` command to see the results in your console.
+
 ### Loading externally
 
 Finally, you can maintain independent data models for each tenant that you would

docs/pages/product/configuration/recipes/data-store-cost-saving-guide.mdx

@@ -1,4 +1,4 @@
-# Data Store Cost Saving Guide
+# Optimizing data source usage
 
 As a semantic layer, Cube supports various [data
 sources][ref-config-data-sources], including cloud-based data warehouses and
@@ -8,7 +8,7 @@ and business intelligence.
 Depending on the upstream data source and the use case, Cube can be configured
 in a way that provides the best economic effect and maximizes cost savings.
 
-## Reducing Data Store Usage
+## Reducing data store usage
 
 Cloud-based data stores commonly use two pricing models: _on-demand_, when you
 get charged for the storage and compute resources used to process each query, or

docs/pages/product/configuration/recipes/multiple-sources-same-schema.mdx

@@ -1,4 +1,4 @@
-# Using multiple data sources
+# Providing a custom data source for each tenant
 
 ## Use case