Deployed f5a1a15 to 12.0 with MkDocs 1.6.1 and mike 2.1.3

12.0/config/env/index.html

@@ -4387,7 +4387,7 @@ <h2 id="s3-storage-backend-configurations-only-valid-in-pro-edition-at-deploying
 <li><code>INIT_S3_USE_HTTPS</code>: Use HTTPS connections to S3 if enabled, default is <code>true</code></li>
 </ul>
 <h2 id="seasearch">SeaSearch<a class="headerlink" href="#seasearch" title="Permanent link">&para;</a></h2>
-<p>For configurations about SeaSearch in <code>.env</code>, please refer <a href="https://seasearch-manual.seafile.comconfig/">here</a> for the details</p>
+<p>For configurations about SeaSearch in <code>.env</code>, please refer <a href="https://seasearch-manual.seafile.com/config/">here</a> for the details</p>
 
 
 

12.0/setup/cluster_deploy_with_docker/index.html

@@ -4344,7 +4344,7 @@ <h2 id="environment">Environment<a class="headerlink" href="#environment" title=
 <p class="admonition-title">Prerequisites</p>
 <ul>
 <li>
-<p>We assume you have already deployed memory cache server (e.g., <strong><em>Memcached</em></strong>), <strong><em>MariaDB</em></strong>, file indexer (e.g., <strong><em>ElasticSearch</em></strong>, <a href="https://seasearch-manual.seafile.com"><em>SeaSearch</em></a>) in separate machines and use <strong><em>S3</em></strong> like object storage. </p>
+<p>We assume you have already deployed memory cache server (e.g., <strong><em>Memcached</em></strong>), <strong><em>MariaDB</em></strong>, file indexer (e.g., <strong><em>ElasticSearch</em></strong>, <a href="https://seasearch-manual.seafile.com/"><em>SeaSearch</em></a>) in separate machines and use <strong><em>S3</em></strong> like object storage. </p>
 </li>
 <li>
 <p>Usually, each node of Seafile Cluster should have at least <strong>2 cores</strong> and <strong>2G memory</strong>. If the above services are deployed together with a node in the Seafile cluster especially <strong><em>ElasticSearch</em></strong>, we recommend that you prepare <strong>4 cores</strong> and <strong>4G memory</strong> for that node</p>

12.0/setup/use_seasearch/index.html

@@ -4144,7 +4144,7 @@
 <h1 id="use-seasearch-as-search-engine-pro">Use SeaSearch as search engine (Pro)<a class="headerlink" href="#use-seasearch-as-search-engine-pro" title="Permanent link">&para;</a></h1>
 <div class="admonition success">
 <p class="admonition-title">New features</p>
-<p><a href="https://seasearch-manual.seafile.com">SeaSearch</a>, a file indexer with more lightweight and efficiency than <em>Elasticsearch</em>, is supported from Seafile 12.</p>
+<p><a href="https://seasearch-manual.seafile.com/">SeaSearch</a>, a file indexer with more lightweight and efficiency than <em>Elasticsearch</em>, is supported from Seafile 12.</p>
 </div>
 <div class="admonition note">
 <p class="admonition-title">For Seafile deploy from binary package</p>
@@ -4160,7 +4160,7 @@ <h2 id="deploy-seasearch-service">Deploy SeaSearch service<a class="headerlink"
 <div class="highlight"><pre><span></span><code>wget<span class="w"> </span>https://manual.seafile.com/12.0/docker/pro/seasearch.yml
 </code></pre></div>
 <h2 id="modify-env">Modify <code>.env</code><a class="headerlink" href="#modify-env" title="Permanent link">&para;</a></h2>
-<p>We have configured the relevant variables in .env. Here you must pay special attention to the following variable information, which will affect the SeaSearch initialization process. For variables in <code>.env</code> of SeaSearch service, please refer <a href="https://seasearch-manual.seafile.comconfig/">here</a> for the details. We use <code>/opt/seasearch-data</code> as the persistent directory of SeaSearch:</p>
+<p>We have configured the relevant variables in .env. Here you must pay special attention to the following variable information, which will affect the SeaSearch initialization process. For variables in <code>.env</code> of SeaSearch service, please refer <a href="https://seasearch-manual.seafile.com/config/">here</a> for the details. We use <code>/opt/seasearch-data</code> as the persistent directory of SeaSearch:</p>
 <div class="admonition warning">
 <p class="admonition-title">For Apple's Chips</p>
 <p>Since Apple's chips (such as M2) do not support <a href="https://www.intel.com/content/www/us/en/developer/tools/oneapi/onemkl.html">MKL</a>, you need to set the relevant image to <code>seafileltd/seasearch-nomkl:latest</code> if you use an Apple's chip:</p>

12.0/setup_binary/cluster_deployment/index.html

@@ -4615,7 +4615,7 @@ <h2 id="environment">Environment<a class="headerlink" href="#environment" title=
 <p class="admonition-title">Prerequisites</p>
 <ul>
 <li>
-<p>We assume you have already deployed memory cache server (e.g., <strong><em>Memcached</em></strong>), <strong><em>MariaDB</em></strong>, file indexer (e.g., <strong><em>ElasticSearch</em></strong>, <a href="https://seasearch-manual.seafile.com"><em>SeaSearch</em></a>) in separate machines and use <strong><em>S3</em></strong> like object storage. </p>
+<p>We assume you have already deployed memory cache server (e.g., <strong><em>Memcached</em></strong>), <strong><em>MariaDB</em></strong>, file indexer (e.g., <strong><em>ElasticSearch</em></strong>, <a href="https://seasearch-manual.seafile.com/"><em>SeaSearch</em></a>) in separate machines and use <strong><em>S3</em></strong> like object storage. </p>
 </li>
 <li>
 <p>Usually, each node of Seafile Cluster should have at least <strong>2 cores</strong> and <strong>2G memory</strong>. If the above services are deployed together with a node in the Seafile cluster especially <strong><em>ElasticSearch</em></strong>, we recommend that you prepare <strong>4 cores</strong> and <strong>4G memory</strong> for that node</p>