mirror of
https://github.com/zadam/trilium.git
synced 2025-12-21 23:59:59 +01:00
feat(docs): document multiple server instances & reorganize
This commit is contained in:
@@ -1,5 +1,6 @@
|
||||
# Manual server installation
|
||||
This page describes manually installing Trilium on your server. **Note that this is a not well supported way to install Trilium, problems may appear, information laid out here is quite out of date. It is recommended to use either Docker or packaged build installation.**
|
||||
# Manually
|
||||
> [!WARNING]
|
||||
> This page describes manually installing Trilium on your server. **Note that this is a not well supported way to install Trilium, problems may appear, information laid out here is quite out of date. It is recommended to use either** <a class="reference-link" href="Using%20Docker.md">Docker Server Installation</a> **or** <a class="reference-link" href="Packaged%20version%20for%20Linux.md">Packaged server installation</a>**.**
|
||||
|
||||
## Requirements
|
||||
|
||||
@@ -0,0 +1,22 @@
|
||||
# Multiple server instances
|
||||
Trilium does not support multiple users. In order to have two or more persons with their own set of notes, multiple server instances must be set up. It is also not possible to use multiple [sync](../../Synchronization.md) servers.
|
||||
|
||||
To allow multiple server instances on a single physical server:
|
||||
|
||||
* For <a class="reference-link" href="Packaged%20version%20for%20Linux.md">Packaged version for Linux</a> or <a class="reference-link" href="Manually.md">Manually</a>, if starting the server manually just specify a different port and data directory per instance:
|
||||
|
||||
```
|
||||
TRILIUM_NETWORK_PORT=8080 TRILIUM_DATA_DIR=/path/to/your/data-dir-A /opt/trilium/trilium.sh
|
||||
```
|
||||
|
||||
For a second instance:
|
||||
|
||||
```
|
||||
TRILIUM_NETWORK_PORT=8081 TRILIUM_DATA_DIR=/path/to/your/data-dir-B /opt/trilium/trilium.sh
|
||||
```
|
||||
|
||||
If using `systemd`, then set the [environment variables in the service configuration](https://serverfault.com/questions/413397/how-to-set-environment-variable-in-systemd-service).
|
||||
* For <a class="reference-link" href="Using%20Docker.md">Using Docker</a>, simply use two different containers, each with their own port binding and data directory.
|
||||
* For <a class="reference-link" href="On%20NixOS.md">On NixOS</a>, the only possible way is to use Docker OCI containers or at least one NixOS container with its own service definition.
|
||||
|
||||
For support or additional context, see the related [GitHub Discussion](https://github.com/orgs/TriliumNext/discussions/1642#discussioncomment-12768808).
|
||||
@@ -1,4 +1,4 @@
|
||||
# NixOS server installation
|
||||
# On NixOS
|
||||
This page describes configuring the Trilium module included in NixOS.
|
||||
|
||||
## Requirements
|
||||
@@ -1,4 +1,4 @@
|
||||
# Packaged server installation
|
||||
# Packaged version for Linux
|
||||
This is essentially Trilium sources + node modules + node.js runtime packaged into one 7z file.
|
||||
|
||||
## Steps
|
||||
@@ -1,4 +1,4 @@
|
||||
# Docker Server Installation
|
||||
# Using Docker
|
||||
Official docker images are published on docker hub for **AMD64**, **ARMv7** and **ARM64/v8**: [https://hub.docker.com/r/triliumnext/notes/](https://hub.docker.com/r/triliumnext/notes/)
|
||||
|
||||
## Prerequisites
|
||||
@@ -50,7 +50,7 @@ Trilium requires a directory on the host system to store its data. This director
|
||||
|
||||
#### Local Access Only
|
||||
|
||||
Run the container to make it accessible only from the localhost. This setup is suitable for testing or when using a proxy server like Nginx or Apache.
|
||||
Run the container to make it accessible only from the localhost. This setup is suitable for testing or when using a prox ay server like Nginx or Apache.
|
||||
|
||||
```
|
||||
sudo docker run -t -i -p 127.0.0.1:8080:8080 -v ~/trilium-data:/home/node/trilium-data triliumnext/notes:[VERSION]
|
||||
@@ -1,4 +1,4 @@
|
||||
# Kubernetes server installation
|
||||
# Using Kubernetes
|
||||
As Trilium can be run in Docker it also can be deployed in Kubernetes. You can either use our Helm chart, a community Helm chart, or roll your own Kubernetes deployment.
|
||||
|
||||
The recommended way is to use a Helm chart.
|
||||
Reference in New Issue
Block a user