mirror of
https://github.com/zadam/trilium.git
synced 2025-10-30 01:36:24 +01:00
chore(docs): fix quick search documentation not in meta
This commit is contained in:
Elian Doran
2
docs/User Guide/!!!meta.json
vendored
2
docs/User Guide/!!!meta.json
vendored
@@ -1,6 +1,6 @@
|
||||
{
|
||||
"formatVersion": 2,
|
||||
"appVersion": "0.97.2",
|
||||
"appVersion": "0.98.0",
|
||||
"files": [
|
||||
{
|
||||
"isClone": false,
|
||||
|
||||
@@ -1,21 +1,22 @@
|
||||
# Configuration (config.ini or environment variables)
|
||||
|
||||
Trilium supports configuration via a file named `config.ini` and environment variables. This document provides a comprehensive reference for all configuration options.
|
||||
|
||||
## Configuration Precedence
|
||||
|
||||
Configuration values are loaded in the following order of precedence (highest to lowest):
|
||||
1. **Environment variables** (checked first)
|
||||
2. **config.ini file values**
|
||||
3. **Default values**
|
||||
|
||||
1. **Environment variables** (checked first)
|
||||
2. **config.ini file values**
|
||||
3. **Default values**
|
||||
|
||||
## Environment Variable Patterns
|
||||
|
||||
Trilium supports multiple environment variable patterns for flexibility. The primary pattern is: `TRILIUM_[SECTION]_[KEY]`
|
||||
|
||||
Where:
|
||||
- `SECTION` is the INI section name in UPPERCASE
|
||||
- `KEY` is the camelCase configuration key converted to UPPERCASE (e.g., `instanceName` → `INSTANCENAME`)
|
||||
|
||||
* `SECTION` is the INI section name in UPPERCASE
|
||||
* `KEY` is the camelCase configuration key converted to UPPERCASE (e.g., `instanceName` → `INSTANCENAME`)
|
||||
|
||||
Additionally, shorter aliases are available for common configurations (see Alternative Variables section below).
|
||||
|
||||
@@ -24,8 +25,8 @@ Additionally, shorter aliases are available for common configurations (see Alter
|
||||
### General Section
|
||||
|
||||
| Environment Variable | Type | Default | Description |
|
||||
|------------------|------|---------|-------------|
|
||||
| `TRILIUM_GENERAL_INSTANCENAME` | string | "" | Instance name for API identification |
|
||||
| --- | --- | --- | --- |
|
||||
| `TRILIUM_GENERAL_INSTANCENAME` | string | "" | Instance name for API identification |
|
||||
| `TRILIUM_GENERAL_NOAUTHENTICATION` | boolean | false | Disable authentication (server only) |
|
||||
| `TRILIUM_GENERAL_NOBACKUP` | boolean | false | Disable automatic backups |
|
||||
| `TRILIUM_GENERAL_NODESKTOPICON` | boolean | false | Disable desktop icon creation |
|
||||
@@ -34,91 +35,97 @@ Additionally, shorter aliases are available for common configurations (see Alter
|
||||
### Network Section
|
||||
|
||||
| Environment Variable | Type | Default | Description |
|
||||
|------------------|------|---------|-------------|
|
||||
| --- | --- | --- | --- |
|
||||
| `TRILIUM_NETWORK_HOST` | string | "0.0.0.0" | Server host binding |
|
||||
| `TRILIUM_NETWORK_PORT` | string | "3000" | Server port |
|
||||
| `TRILIUM_NETWORK_HTTPS` | boolean | false | Enable HTTPS |
|
||||
| `TRILIUM_NETWORK_CERTPATH` | string | "" | SSL certificate path |
|
||||
| `TRILIUM_NETWORK_KEYPATH` | string | "" | SSL key path |
|
||||
| `TRILIUM_NETWORK_CERTPATH` | string | "" | SSL certificate path |
|
||||
| `TRILIUM_NETWORK_KEYPATH` | string | "" | SSL key path |
|
||||
| `TRILIUM_NETWORK_TRUSTEDREVERSEPROXY` | boolean/string | false | Reverse proxy trust settings |
|
||||
| `TRILIUM_NETWORK_CORSALLOWORIGIN` | string | "" | CORS allowed origins |
|
||||
| `TRILIUM_NETWORK_CORSALLOWMETHODS` | string | "" | CORS allowed methods |
|
||||
| `TRILIUM_NETWORK_CORSALLOWHEADERS` | string | "" | CORS allowed headers |
|
||||
| `TRILIUM_NETWORK_CORSALLOWORIGIN` | string | "" | CORS allowed origins |
|
||||
| `TRILIUM_NETWORK_CORSALLOWMETHODS` | string | "" | CORS allowed methods |
|
||||
| `TRILIUM_NETWORK_CORSALLOWHEADERS` | string | "" | CORS allowed headers |
|
||||
|
||||
### Session Section
|
||||
|
||||
| Environment Variable | Type | Default | Description |
|
||||
|------------------|------|---------|-------------|
|
||||
| --- | --- | --- | --- |
|
||||
| `TRILIUM_SESSION_COOKIEMAXAGE` | integer | 1814400 | Session cookie max age in seconds (21 days) |
|
||||
|
||||
### Sync Section
|
||||
|
||||
| Environment Variable | Type | Default | Description |
|
||||
|------------------|------|---------|-------------|
|
||||
| `TRILIUM_SYNC_SYNCSERVERHOST` | string | "" | Sync server host URL |
|
||||
| --- | --- | --- | --- |
|
||||
| `TRILIUM_SYNC_SYNCSERVERHOST` | string | "" | Sync server host URL |
|
||||
| `TRILIUM_SYNC_SYNCSERVERTIMEOUT` | string | "120000" | Sync server timeout in milliseconds |
|
||||
| `TRILIUM_SYNC_SYNCPROXY` | string | "" | Sync proxy URL |
|
||||
| `TRILIUM_SYNC_SYNCPROXY` | string | "" | Sync proxy URL |
|
||||
|
||||
### MultiFactorAuthentication Section
|
||||
|
||||
| Environment Variable | Type | Default | Description |
|
||||
|------------------|------|---------|-------------|
|
||||
| `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHBASEURL` | string | "" | OAuth/OpenID base URL |
|
||||
| `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHCLIENTID` | string | "" | OAuth client ID |
|
||||
| `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHCLIENTSECRET` | string | "" | OAuth client secret |
|
||||
| `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHISSUERBASEURL` | string | "https://accounts.google.com" | OAuth issuer base URL |
|
||||
| --- | --- | --- | --- |
|
||||
| `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHBASEURL` | string | "" | OAuth/OpenID base URL |
|
||||
| `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHCLIENTID` | string | "" | OAuth client ID |
|
||||
| `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHCLIENTSECRET` | string | "" | OAuth client secret |
|
||||
| `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHISSUERBASEURL` | string | "[https://accounts.google.com](https://accounts.google.com)" | OAuth issuer base URL |
|
||||
| `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHISSUERNAME` | string | "Google" | OAuth issuer display name |
|
||||
| `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHISSUERICON` | string | "" | OAuth issuer icon URL |
|
||||
| `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHISSUERICON` | string | "" | OAuth issuer icon URL |
|
||||
|
||||
### Logging Section
|
||||
|
||||
| Environment Variable | Type | Default | Description |
|
||||
|------------------|------|---------|-------------|
|
||||
| `TRILIUM_LOGGING_RETENTIONDAYS` | integer | 90 | Number of days to retain log files |
|
||||
| --- | --- | --- | --- |
|
||||
| `TRILIUM_LOGGING_RETENTIONDAYS` | integer | 90 | Number of days to retain log files |
|
||||
|
||||
## Alternative Environment Variables
|
||||
|
||||
The following alternative environment variable names are also supported and work identically to their longer counterparts:
|
||||
|
||||
### Network CORS Variables
|
||||
- `TRILIUM_NETWORK_CORS_ALLOW_ORIGIN` (alternative to `TRILIUM_NETWORK_CORSALLOWORIGIN`)
|
||||
- `TRILIUM_NETWORK_CORS_ALLOW_METHODS` (alternative to `TRILIUM_NETWORK_CORSALLOWMETHODS`)
|
||||
- `TRILIUM_NETWORK_CORS_ALLOW_HEADERS` (alternative to `TRILIUM_NETWORK_CORSALLOWHEADERS`)
|
||||
|
||||
* `TRILIUM_NETWORK_CORS_ALLOW_ORIGIN` (alternative to `TRILIUM_NETWORK_CORSALLOWORIGIN`)
|
||||
* `TRILIUM_NETWORK_CORS_ALLOW_METHODS` (alternative to `TRILIUM_NETWORK_CORSALLOWMETHODS`)
|
||||
* `TRILIUM_NETWORK_CORS_ALLOW_HEADERS` (alternative to `TRILIUM_NETWORK_CORSALLOWHEADERS`)
|
||||
|
||||
### Sync Variables
|
||||
- `TRILIUM_SYNC_SERVER_HOST` (alternative to `TRILIUM_SYNC_SYNCSERVERHOST`)
|
||||
- `TRILIUM_SYNC_SERVER_TIMEOUT` (alternative to `TRILIUM_SYNC_SYNCSERVERTIMEOUT`)
|
||||
- `TRILIUM_SYNC_SERVER_PROXY` (alternative to `TRILIUM_SYNC_SYNCPROXY`)
|
||||
|
||||
* `TRILIUM_SYNC_SERVER_HOST` (alternative to `TRILIUM_SYNC_SYNCSERVERHOST`)
|
||||
* `TRILIUM_SYNC_SERVER_TIMEOUT` (alternative to `TRILIUM_SYNC_SYNCSERVERTIMEOUT`)
|
||||
* `TRILIUM_SYNC_SERVER_PROXY` (alternative to `TRILIUM_SYNC_SYNCPROXY`)
|
||||
|
||||
### OAuth/MFA Variables
|
||||
- `TRILIUM_OAUTH_BASE_URL` (alternative to `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHBASEURL`)
|
||||
- `TRILIUM_OAUTH_CLIENT_ID` (alternative to `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHCLIENTID`)
|
||||
- `TRILIUM_OAUTH_CLIENT_SECRET` (alternative to `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHCLIENTSECRET`)
|
||||
- `TRILIUM_OAUTH_ISSUER_BASE_URL` (alternative to `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHISSUERBASEURL`)
|
||||
- `TRILIUM_OAUTH_ISSUER_NAME` (alternative to `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHISSUERNAME`)
|
||||
- `TRILIUM_OAUTH_ISSUER_ICON` (alternative to `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHISSUERICON`)
|
||||
|
||||
* `TRILIUM_OAUTH_BASE_URL` (alternative to `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHBASEURL`)
|
||||
* `TRILIUM_OAUTH_CLIENT_ID` (alternative to `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHCLIENTID`)
|
||||
* `TRILIUM_OAUTH_CLIENT_SECRET` (alternative to `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHCLIENTSECRET`)
|
||||
* `TRILIUM_OAUTH_ISSUER_BASE_URL` (alternative to `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHISSUERBASEURL`)
|
||||
* `TRILIUM_OAUTH_ISSUER_NAME` (alternative to `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHISSUERNAME`)
|
||||
* `TRILIUM_OAUTH_ISSUER_ICON` (alternative to `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHISSUERICON`)
|
||||
|
||||
### Logging Variables
|
||||
- `TRILIUM_LOGGING_RETENTION_DAYS` (alternative to `TRILIUM_LOGGING_RETENTIONDAYS`)
|
||||
|
||||
* `TRILIUM_LOGGING_RETENTION_DAYS` (alternative to `TRILIUM_LOGGING_RETENTIONDAYS`)
|
||||
|
||||
## Boolean Values
|
||||
|
||||
Boolean environment variables accept the following values:
|
||||
- **True**: `"true"`, `"1"`, `1`
|
||||
- **False**: `"false"`, `"0"`, `0`
|
||||
- Any other value defaults to `false`
|
||||
|
||||
* **True**: `"true"`, `"1"`, `1`
|
||||
* **False**: `"false"`, `"0"`, `0`
|
||||
* Any other value defaults to `false`
|
||||
|
||||
## Using Environment Variables
|
||||
|
||||
Both naming patterns are fully supported and can be used interchangeably:
|
||||
|
||||
- The longer format follows the section/key pattern for consistency with the INI file structure
|
||||
- The shorter alternatives provide convenience for common configurations
|
||||
- You can use whichever format you prefer - both are equally valid
|
||||
* The longer format follows the section/key pattern for consistency with the INI file structure
|
||||
* The shorter alternatives provide convenience for common configurations
|
||||
* You can use whichever format you prefer - both are equally valid
|
||||
|
||||
## Examples
|
||||
|
||||
### Docker Compose Example
|
||||
|
||||
```yaml
|
||||
services:
|
||||
trilium:
|
||||
@@ -138,7 +145,8 @@ services:
|
||||
```
|
||||
|
||||
### Shell Export Example
|
||||
```bash
|
||||
|
||||
```sh
|
||||
# Using either format
|
||||
export TRILIUM_GENERAL_NOAUTHENTICATION=false
|
||||
export TRILIUM_NETWORK_HTTPS=true
|
||||
|
||||
@@ -1,53 +0,0 @@
|
||||
# Quick Search - Exact Match Operator
|
||||
|
||||
## Overview
|
||||
|
||||
Quick Search now supports the exact match operator (`=`) at the beginning of your search query. This allows you to search for notes where the title or content exactly matches your search term, rather than just containing it.
|
||||
|
||||
## Usage
|
||||
|
||||
To use exact match in Quick Search:
|
||||
|
||||
1. Start your search query with the `=` operator
|
||||
2. Follow it immediately with your search term (no space after `=`)
|
||||
|
||||
### Examples
|
||||
|
||||
- `=example` - Finds notes with title exactly "example" or content exactly "example"
|
||||
- `=Project Plan` - Finds notes with title exactly "Project Plan" or content exactly "Project Plan"
|
||||
- `='hello world'` - Use quotes for multi-word exact matches
|
||||
|
||||
### Comparison with Regular Search
|
||||
|
||||
| Query | Behavior |
|
||||
|-------|----------|
|
||||
| `example` | Finds all notes containing "example" anywhere in title or content |
|
||||
| `=example` | Finds only notes where the title equals "example" or content equals "example" exactly |
|
||||
|
||||
## Technical Details
|
||||
|
||||
When you use the `=` operator:
|
||||
- The search performs an exact match on note titles
|
||||
- For note content, it looks for exact matches of the entire content
|
||||
- Partial word matches are excluded
|
||||
- The search is case-insensitive
|
||||
|
||||
## Limitations
|
||||
|
||||
- The `=` operator must be at the very beginning of the search query
|
||||
- Spaces after `=` will treat it as a regular search
|
||||
- Multiple `=` operators (like `==example`) are treated as regular text search
|
||||
|
||||
## Use Cases
|
||||
|
||||
This feature is particularly useful when:
|
||||
- You know the exact title of a note
|
||||
- You want to find notes with specific, complete content
|
||||
- You need to distinguish between notes with similar but not identical titles
|
||||
- You want to avoid false positives from partial matches
|
||||
|
||||
## Related Features
|
||||
|
||||
- For more complex exact matching queries, use the full [Search](Search.md) functionality
|
||||
- For fuzzy matching (finding results despite typos), use the `~=` operator in the full search
|
||||
- For partial matches with wildcards, use operators like `*=*`, `=*`, or `*=` in the full search
|
||||
@@ -3,16 +3,16 @@
|
||||
|
||||
The _Quick search_ function does a full-text search (that is, it searches through the content of notes and not just the title of a note) and displays the result in an easy-to-access manner.
|
||||
|
||||
The alternative to the quick search is the <a class="reference-link" href="Search.md">Search</a> function, which opens in a dedicated tab and has support for advanced queries.
|
||||
The alternative to the quick search is the <a class="reference-link" href="Search.md">Search</a> function, which opens in a dedicated tab and has support for advanced queries.
|
||||
|
||||
For even faster navigation, it's possible to use <a class="reference-link" href="Jump%20to.md">Jump to Note</a> which will only search through the note titles instead of the content.
|
||||
For even faster navigation, it's possible to use <a class="reference-link" href="Jump%20to.md">Jump to...</a> which will only search through the note titles instead of the content.
|
||||
|
||||
## Layout
|
||||
|
||||
Based on the <a class="reference-link" href="../UI%20Elements/Vertical%20and%20horizontal%20layout.md">Vertical and horizontal layout</a>, the quick search is placed:
|
||||
Based on the <a class="reference-link" href="../UI%20Elements/Vertical%20and%20horizontal%20layout.md">Vertical and horizontal layout</a>, the quick search is placed:
|
||||
|
||||
* On the vertical layout, it is displayed right above the <a class="reference-link" href="../UI%20Elements/Note%20Tree.md">Note Tree</a>.
|
||||
* On the horizontal layout, it is displayed in the <a class="reference-link" href="../UI%20Elements/Launch%20Bar.md">Launch Bar</a>, where it can be positioned just like any other icon.
|
||||
* On the vertical layout, it is displayed right above the <a class="reference-link" href="../UI%20Elements/Note%20Tree.md">Note Tree</a>.
|
||||
* On the horizontal layout, it is displayed in the <a class="reference-link" href="../UI%20Elements/Launch%20Bar.md">Launch Bar</a>, where it can be positioned just like any other icon.
|
||||
|
||||
## Search Features
|
||||
|
||||
@@ -56,4 +56,58 @@ Quick search uses progressive search:
|
||||
2. **Content previews**: 200-character snippets show match context
|
||||
3. **Infinite scrolling**: Additional results load on scroll
|
||||
4. **Specific terms**: Specific search terms return more focused results
|
||||
5. **Match locations**: Bold text indicates where matches occur
|
||||
5. **Match locations**: Bold text indicates where matches occur
|
||||
|
||||
## Quick Search - Exact Match Operator
|
||||
|
||||
Quick Search now supports the exact match operator (`=`) at the beginning of your search query. This allows you to search for notes where the title or content exactly matches your search term, rather than just containing it.
|
||||
|
||||
### Usage
|
||||
|
||||
To use exact match in Quick Search:
|
||||
|
||||
1. Start your search query with the `=` operator
|
||||
2. Follow it immediately with your search term (no space after `=`)
|
||||
|
||||
#### Examples
|
||||
|
||||
* `=example` - Finds notes with title exactly "example" or content exactly "example"
|
||||
* `=Project Plan` - Finds notes with title exactly "Project Plan" or content exactly "Project Plan"
|
||||
* `='hello world'` - Use quotes for multi-word exact matches
|
||||
|
||||
#### Comparison with Regular Search
|
||||
|
||||
| Query | Behavior |
|
||||
| --- | --- |
|
||||
| `example` | Finds all notes containing "example" anywhere in title or content |
|
||||
| `=example` | Finds only notes where the title equals "example" or content equals "example" exactly |
|
||||
|
||||
### Technical Details
|
||||
|
||||
When you use the `=` operator:
|
||||
|
||||
* The search performs an exact match on note titles
|
||||
* For note content, it looks for exact matches of the entire content
|
||||
* Partial word matches are excluded
|
||||
* The search is case-insensitive
|
||||
|
||||
### Limitations
|
||||
|
||||
* The `=` operator must be at the very beginning of the search query
|
||||
* Spaces after `=` will treat it as a regular search
|
||||
* Multiple `=` operators (like `==example`) are treated as regular text search
|
||||
|
||||
### Use Cases
|
||||
|
||||
This feature is particularly useful when:
|
||||
|
||||
* You know the exact title of a note
|
||||
* You want to find notes with specific, complete content
|
||||
* You need to distinguish between notes with similar but not identical titles
|
||||
* You want to avoid false positives from partial matches
|
||||
|
||||
### Related Features
|
||||
|
||||
* For more complex exact matching queries, use the full [Search](Search.md) functionality
|
||||
* For fuzzy matching (finding results despite typos), use the `~=` operator in the full search
|
||||
* For partial matches with wildcards, use operators like `*=*`, `=*`, or `*=` in the full search
|
||||
@@ -187,7 +187,7 @@ docker run -d --name trilium -p 8080:8080 --user $(id -u):$(id -g) -v ~/trilium-
|
||||
* `TRILIUM_GID`: GID to use for the container process (passed to Docker's `--user` flag)
|
||||
* `TRILIUM_DATA_DIR`: Path to the data directory inside the container (default: `/home/node/trilium-data`)
|
||||
|
||||
For a complete list of configuration environment variables (network settings, authentication, sync, etc.), see <a class="reference-link" href="../../Advanced%20Usage/Configuration%20(config.ini%20or%20e.md">Configuration (config.ini or environment variables)</a>.
|
||||
For a complete list of configuration environment variables (network settings, authentication, sync, etc.), see <a class="reference-link" href="#root/dmi3wz9muS2O">Configuration (config.ini or environment variables)</a>.
|
||||
|
||||
### Volume Permissions
|
||||
|
||||
|
||||
@@ -38,8 +38,8 @@ In order to setup OpenID, you will need to setup a authentication provider. This
|
||||
|
||||
1. Set the `oauthBaseUrl`, `oauthClientId` and `oauthClientSecret` in the `config.ini` file (check <a class="reference-link" href="../../Advanced%20Usage/Configuration%20(config.ini%20or%20e.md">Configuration (config.ini or environment variables)</a> for more information).
|
||||
1. You can also setup through environment variables:
|
||||
- Standard: `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHBASEURL`, `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHCLIENTID`, `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHCLIENTSECRET`
|
||||
- Legacy (still supported): `TRILIUM_OAUTH_BASE_URL`, `TRILIUM_OAUTH_CLIENT_ID`, `TRILIUM_OAUTH_CLIENT_SECRET`
|
||||
* Standard: `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHBASEURL`, `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHCLIENTID`, `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHCLIENTSECRET`
|
||||
* Legacy (still supported): `TRILIUM_OAUTH_BASE_URL`, `TRILIUM_OAUTH_CLIENT_ID`, `TRILIUM_OAUTH_CLIENT_SECRET`
|
||||
2. `oauthBaseUrl` should be the link of your Trilium instance server, for example, `https://<your-trilium-domain>`.
|
||||
2. Restart the server
|
||||
3. Go to "Menu" -> "Options" -> "MFA"
|
||||
@@ -49,8 +49,9 @@ In order to setup OpenID, you will need to setup a authentication provider. This
|
||||
|
||||
> [!NOTE]
|
||||
> The default OAuth issuer is Google. To use other services such as Authentik or Auth0, you can configure the settings via `oauthIssuerBaseUrl`, `oauthIssuerName`, and `oauthIssuerIcon` in the `config.ini` file. Alternatively, these values can be set using environment variables:
|
||||
> - Standard: `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHISSUERBASEURL`, `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHISSUERNAME`, `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHISSUERICON`
|
||||
> - Legacy (still supported): `TRILIUM_OAUTH_ISSUER_BASE_URL`, `TRILIUM_OAUTH_ISSUER_NAME`, `TRILIUM_OAUTH_ISSUER_ICON`
|
||||
>
|
||||
> * Standard: `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHISSUERBASEURL`, `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHISSUERNAME`, `TRILIUM_MULTIFACTORAUTHENTICATION_OAUTHISSUERICON`
|
||||
> * Legacy (still supported): `TRILIUM_OAUTH_ISSUER_BASE_URL`, `TRILIUM_OAUTH_ISSUER_NAME`, `TRILIUM_OAUTH_ISSUER_ICON`
|
||||
>
|
||||
> `oauthIssuerName` and `oauthIssuerIcon` are required for displaying correct issuer information at the Login page.
|
||||
|
||||
|
||||
@@ -27,7 +27,7 @@ keyPath=/[username]/.acme.sh/[hostname]/example.com.key
|
||||
|
||||
You can also review the [configuration](../../Advanced%20Usage/Configuration%20\(config.ini%20or%20e.md) file to provide all `config.ini` values as environment variables instead. For example, you can configure TLS using environment variables:
|
||||
|
||||
```bash
|
||||
```sh
|
||||
export TRILIUM_NETWORK_HTTPS=true
|
||||
export TRILIUM_NETWORK_CERTPATH=/path/to/cert.pem
|
||||
export TRILIUM_NETWORK_KEYPATH=/path/to/key.pem
|
||||
|
||||
Reference in New Issue
Block a user