mirror of
https://github.com/zadam/trilium.git
synced 2025-11-02 03:16:11 +01:00
docs(user): minor tweaks to TLS installation
This commit is contained in:
20
docs/User Guide/!!!meta.json
vendored
20
docs/User Guide/!!!meta.json
vendored
@@ -755,7 +755,7 @@
|
||||
"WOcw2SLH6tbX",
|
||||
"l2VkvOwUNfZj"
|
||||
],
|
||||
"title": "TLS Configuration",
|
||||
"title": "HTTPS (TLS)",
|
||||
"notePosition": 100,
|
||||
"prefix": null,
|
||||
"isExpanded": false,
|
||||
@@ -789,10 +789,24 @@
|
||||
"value": "tls-configuration",
|
||||
"isInheritable": false,
|
||||
"position": 20
|
||||
},
|
||||
{
|
||||
"type": "relation",
|
||||
"name": "internalLink",
|
||||
"value": "vcjrb3VVYPZI",
|
||||
"isInheritable": false,
|
||||
"position": 40
|
||||
},
|
||||
{
|
||||
"type": "label",
|
||||
"name": "iconClass",
|
||||
"value": "bx bx-lock-alt",
|
||||
"isInheritable": false,
|
||||
"position": 50
|
||||
}
|
||||
],
|
||||
"format": "markdown",
|
||||
"dataFileName": "TLS Configuration.md",
|
||||
"dataFileName": "HTTPS (TLS).md",
|
||||
"attachments": []
|
||||
},
|
||||
{
|
||||
@@ -835,7 +849,7 @@
|
||||
{
|
||||
"type": "label",
|
||||
"name": "iconClass",
|
||||
"value": "bx bx-lock-alt",
|
||||
"value": "bx bx-user",
|
||||
"isInheritable": false,
|
||||
"position": 10
|
||||
}
|
||||
|
||||
@@ -9,7 +9,7 @@ To install Trilium on your desktop, follow these steps:
|
||||
|
||||
Trilium offers various startup scripts to customize your experience:
|
||||
|
||||
* `trilium-no-cert-check`: Starts Trilium without validating [TLS certificates](Server%20Installation/TLS%20Configuration.md), useful if connecting to a server with a self-signed certificate.
|
||||
* `trilium-no-cert-check`: Starts Trilium without validating [TLS certificates](Server%20Installation/HTTPS%20\(TLS\).md), useful if connecting to a server with a self-signed certificate.
|
||||
* Alternatively, set the `NODE_TLS_REJECT_UNAUTHORIZED=0` environment variable before starting Trilium.
|
||||
* `trilium-portable`: Launches Trilium in portable mode, where the [data directory](Data%20directory.md) is created within the application's directory, making it easy to move the entire setup.
|
||||
* `trilium-safe-mode`: Boots Trilium in "safe mode," disabling any startup scripts that might cause the application to crash.
|
||||
|
||||
@@ -18,7 +18,7 @@ The server installation includes both web and [mobile frontends](Mobile%20Fronte
|
||||
|
||||
## Configuration
|
||||
|
||||
After setting up your server installation, you may want to configure settings such as the port or enable [TLS](Server%20Installation/TLS%20Configuration.md). Configuration is managed via the Trilium `config.ini` file, which is located in the [data directory](Data%20directory.md) by default. To begin customizing your setup, copy the provided `config-sample.ini` file with default values to `config.ini`.
|
||||
After setting up your server installation, you may want to configure settings such as the port or enable [TLS](Server%20Installation/HTTPS%20\(TLS\).md). Configuration is managed via the Trilium `config.ini` file, which is located in the [data directory](Data%20directory.md) by default. To begin customizing your setup, copy the provided `config-sample.ini` file with default values to `config.ini`.
|
||||
|
||||
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.
|
||||
|
||||
|
||||
@@ -62,4 +62,4 @@ The application by default starts up on port 8080, so you can open your browser
|
||||
|
||||
## TLS
|
||||
|
||||
Don't forget to [configure TLS](../TLS%20Configuration.md) which is required for secure usage!
|
||||
Don't forget to [configure TLS](../HTTPS%20\(TLS\).md) which is required for secure usage!
|
||||
@@ -178,4 +178,4 @@ If you get an error like this, you need to either upgrade your glibc (typically
|
||||
|
||||
## TLS
|
||||
|
||||
Don't forget to [configure TLS](../TLS%20Configuration.md), which is required for secure usage!
|
||||
Don't forget to [configure TLS](../HTTPS%20\(TLS\).md), which is required for secure usage!
|
||||
@@ -1,7 +1,8 @@
|
||||
# TLS Configuration
|
||||
# HTTPS (TLS)
|
||||
Configuring TLS is essential for [server installation](../Server%20Installation.md) in Trilium. This guide details the steps to set up TLS within Trilium itself.
|
||||
|
||||
For a more robust solution, consider using TLS termination with a reverse proxy (recommended, e.g., Nginx). You can follow a [guide like this](https://www.digitalocean.com/community/tutorials/how-to-secure-nginx-with-let-s-encrypt-on-ubuntu-20-04) for such setups.
|
||||
> [!TIP]
|
||||
> While Trilium supports HTTPS on its own, it's generally a good idea to use a [reverse proxy](2.%20Reverse%20proxy) instead with TLS termination. You can follow a [guide like this](https://www.digitalocean.com/community/tutorials/how-to-secure-nginx-with-let-s-encrypt-on-ubuntu-20-04) for such setups.
|
||||
|
||||
## Obtaining a TLS Certificate
|
||||
|
||||
@@ -9,7 +9,7 @@ In this setup, a central server (referred to as the _sync server_) and multiple
|
||||
|
||||
### Security Considerations
|
||||
|
||||
Setting up the server securely is critical and can be complex. It is crucial to use a valid [TLS certificate](Server%20Installation/TLS%20Configuration.md) (HTTPS) rather than an unencrypted HTTP connection to ensure security and avoid potential vulnerabilities.
|
||||
Setting up the server securely is critical and can be complex. It is crucial to use a valid [TLS certificate](Server%20Installation/HTTPS%20\(TLS\).md) (HTTPS) rather than an unencrypted HTTP connection to ensure security and avoid potential vulnerabilities.
|
||||
|
||||
### Synchronizing a Desktop Instance with a Sync Server
|
||||
|
||||
|
||||
Reference in New Issue
Block a user