From c0d70fcafcd58c8122c12a07f963c0cff705e695 Mon Sep 17 00:00:00 2001 From: Simon Hammes Date: Tue, 7 Apr 2026 14:31:00 +0200 Subject: [PATCH] Fix invalid links --- docs/introduction/architecture.md | 6 +++--- docs/maintenance/backup-recovery.md | 10 +++++----- docs/upgrade/extra-upgrade-notice.md | 2 +- docs/upgrade/upgrade-manual.md | 2 +- 4 files changed, 10 insertions(+), 10 deletions(-) diff --git a/docs/introduction/architecture.md b/docs/introduction/architecture.md index f7f83012..b67dc7f8 100644 --- a/docs/introduction/architecture.md +++ b/docs/introduction/architecture.md @@ -8,7 +8,7 @@ description: Overview of SeaTable Server's Docker-based architecture, including SeaTable Server uses Docker/Docker Compose for easy deployment and upgrades. -A SeaTable Server instance consists of a handful of Docker containers. The following diagram is a simplified representation of the required Docker containers deployed in the [single node setup](../../installation/basic-setup.md). +A SeaTable Server instance consists of a handful of Docker containers. The following diagram is a simplified representation of the required Docker containers deployed in the [single node setup](../installation/basic-setup.md). ```mermaid flowchart TB @@ -191,7 +191,7 @@ By default, SeaTable Server stores user data in the following structure on the l These directories contain the following content: - **conf**: configuration files for SeaTable Server components (see [Configuration](../configuration/overview.md)) -- **logs**: log files generated by SeaTable Server components (see [Logging](../../maintenance/logs.md)) +- **logs**: log files generated by SeaTable Server components (see [Logging](../maintenance/logs.md)) - **db-data**: data stored in big data storage - **seahub-data**: avatars and image thumbnails - **storage-data**: base data, base snapshots, and backup of big data @@ -199,7 +199,7 @@ These directories contain the following content: `/opt/seatable-server/` is mounted as a Docker volume in the Docker container `seatable-server` when SeaTable Server is started. -SeaTable can, depending on the [configuration](../../installation/advanced/s3.md), store the following items in S3 buckets instead of in the file system: +SeaTable can, depending on the [configuration](../installation/advanced/s3.md), store the following items in S3 buckets instead of in the file system: - storage-data - seafile-data diff --git a/docs/maintenance/backup-recovery.md b/docs/maintenance/backup-recovery.md index 61b1c94e..266758e2 100644 --- a/docs/maintenance/backup-recovery.md +++ b/docs/maintenance/backup-recovery.md @@ -6,11 +6,11 @@ description: Complete guide to backing up and restoring a SeaTable Server, inclu If you decide to run your own SeaTable Server, it is essential to ensure that you have a backup in place. -To understand what needs to be backed up, you must first understand the architecture of a SeaTable Server. If you have not yet read the [relevant chapter](../../introduction/architecture.md), please do so now. +To understand what needs to be backed up, you must first understand the architecture of a SeaTable Server. If you have not yet read the [relevant chapter](../introduction/architecture.md), please do so now. !!! success "Backup container for single-node server" - For single-node servers, we offer a [user-friendly backup container](../../installation/components/restic.md) that simplifies the process. Even with this tool, it is important to read this article to gain a thorough understanding of SeaTable backup procedures. + For single-node servers, we offer a [user-friendly backup container](../installation/components/restic.md) that simplifies the process. Even with this tool, it is important to read this article to gain a thorough understanding of SeaTable backup procedures. This article details what should and must be included in your backup, providing you with the knowledge to create your own backup procedure. @@ -69,7 +69,7 @@ Let us clarify where you find which content and how we should backup them. !!! warning "Base data is not stored in the MariaDB database" - A common misunderstanding is the assumption that the content of SeaTable bases is stored in the MariaDB container. This is not the case. Refer to the chapter about [SeaTable architecture](../../introduction/architecture.md) for more details. + A common misunderstanding is the assumption that the content of SeaTable bases is stored in the MariaDB container. This is not the case. Refer to the chapter about [SeaTable architecture](../introduction/architecture.md) for more details. SeaTable creates three databases in the `mariadb` Docker container, storing these kind of data types: @@ -176,7 +176,7 @@ This section covers typical custom cases and provides additional advanced topics ??? success "S3 Object storage instead of local storage" - If you're using [S3 Object Storage](../../installation/advanced/s3.md) instead of local storage, the folders `storage-data` and `seafile-data` aren't stored on the local file system. Instead, all data is stored in four S3 buckets. Three buckets `fs`, `commits` and `blocks` contain assets from file/image column and `storage` contains the base data. + If you're using [S3 Object Storage](../installation/advanced/s3.md) instead of local storage, the folders `storage-data` and `seafile-data` aren't stored on the local file system. Instead, all data is stored in four S3 buckets. Three buckets `fs`, `commits` and `blocks` contain assets from file/image column and `storage` contains the base data. A recommended backup method would be to implement an S3 sync with active versioning and lifecycle management. @@ -216,7 +216,7 @@ The following steps guide you through a complete restore of your SeaTable Server ### 1. Install a fresh SeaTable Server -Follow the [basic setup](../../installation/basic-setup.md) up to and including `docker compose up -d`. Wait for the initial setup to complete successfully, then stop all containers: +Follow the [basic setup](../installation/basic-setup.md) up to and including `docker compose up -d`. Wait for the initial setup to complete successfully, then stop all containers: ```bash cd /opt/seatable-compose diff --git a/docs/upgrade/extra-upgrade-notice.md b/docs/upgrade/extra-upgrade-notice.md index 7d445f8b..da978cb9 100644 --- a/docs/upgrade/extra-upgrade-notice.md +++ b/docs/upgrade/extra-upgrade-notice.md @@ -227,7 +227,7 @@ Of course, you can skip this script and make the changes manually. The following If you're using S3 object storage for files and pictures AND have Memcached configured in your `seafile.conf` file, it is crucial that you update your configuration. Otherwise you can ignore this notice. - Please follow the instructions in our help article about [caching for S3](../../installation/advanced/s3.md#s3-for-files-and-pictures). + Please follow the instructions in our help article about [caching for S3](../installation/advanced/s3.md#s3-for-files-and-pictures). ??? info "New Snapshot and Backup Retention Strategy" diff --git a/docs/upgrade/upgrade-manual.md b/docs/upgrade/upgrade-manual.md index d4bf20d9..f8d912f3 100644 --- a/docs/upgrade/upgrade-manual.md +++ b/docs/upgrade/upgrade-manual.md @@ -35,7 +35,7 @@ docker compose up -d After some seconds your SeaTable Server should be reachable again. You can check the current version of your SeaTable Server opening the URL `https:///server-info`. -Now, you should login as system administrator, switch to the system admin area, and update the plugins as well. You can find more information about the [updating the plugins here](../../configuration/plugins.md). +Now, you should login as system administrator, switch to the system admin area, and update the plugins as well. You can find more information about the [updating the plugins here](../configuration/plugins.md). ## Version specific changes and configurations