mirror of
https://github.com/haiwen/seafile-admin-docs.git
synced 2025-12-26 02:32:50 +00:00
Deployed 2d2169d2 to 13.0 with MkDocs 1.6.1 and mike 2.1.3
This commit is contained in:
parent
eaf96f02de
commit
52d24dc9b7
|
|
@ -4504,6 +4504,15 @@
|
|||
<nav class="md-nav" aria-label="12.0">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#12014-2025-05-28" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
12.0.14 (2025-05-28)
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#12013-2025-05-09" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
|
@ -6242,6 +6251,15 @@
|
|||
<nav class="md-nav" aria-label="12.0">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#12014-2025-05-28" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
12.0.14 (2025-05-28)
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#12013-2025-05-09" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
|
@ -7908,6 +7926,11 @@
|
|||
<h2 id="120">12.0<a class="headerlink" href="#120" title="Permanent link">¶</a></h2>
|
||||
<p><strong>Upgrade</strong></p>
|
||||
<p>Please check our document for how to upgrade to <a href="../../upgrade/upgrade_notes_for_12.0.x/">12.0</a></p>
|
||||
<h3 id="12014-2025-05-28">12.0.14 (2025-05-28)<a class="headerlink" href="#12014-2025-05-28" title="Permanent link">¶</a></h3>
|
||||
<ul>
|
||||
<li>[fix] Fix two stored XSS issues (In rendering terms and conditions and in institution admin page)</li>
|
||||
<li>[fix] Do not close the search popover when click a result</li>
|
||||
</ul>
|
||||
<h3 id="12013-2025-05-09">12.0.13 (2025-05-09)<a class="headerlink" href="#12013-2025-05-09" title="Permanent link">¶</a></h3>
|
||||
<ul>
|
||||
<li>Add S/MIME support for emails</li>
|
||||
|
|
|
|||
|
|
@ -4527,6 +4527,15 @@
|
|||
<nav class="md-nav" aria-label="9.0">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#9014-20250616" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
9.0.14 (2025/06/16)
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#9013-20250402" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
|
@ -6113,6 +6122,15 @@
|
|||
<nav class="md-nav" aria-label="9.0">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#9014-20250616" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
9.0.14 (2025/06/16)
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#9013-20250402" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
|
@ -7645,6 +7663,16 @@
|
|||
|
||||
<h1 id="seafile-client-changelog">Seafile Client Changelog<a class="headerlink" href="#seafile-client-changelog" title="Permanent link">¶</a></h1>
|
||||
<h2 id="90">9.0<a class="headerlink" href="#90" title="Permanent link">¶</a></h2>
|
||||
<h3 id="9014-20250616">9.0.14 (2025/06/16)<a class="headerlink" href="#9014-20250616" title="Permanent link">¶</a></h3>
|
||||
<ul>
|
||||
<li>Improve cloud file browser dialog</li>
|
||||
<li>Improve icons for system notification area</li>
|
||||
<li>Add link to FAQ in file sync error dialog</li>
|
||||
<li>Check and notify when client uses wrong key for encryption</li>
|
||||
<li>Update some seahub APIs</li>
|
||||
<li>Update grandparent modification time when file is updated</li>
|
||||
<li>[win] Skip syncing special legacy folders under Documents ("My Music", "My Pictures" and "My Videos"), to avoid permission errors</li>
|
||||
</ul>
|
||||
<h3 id="9013-20250402">9.0.13 (2025/04/02)<a class="headerlink" href="#9013-20250402" title="Permanent link">¶</a></h3>
|
||||
<ul>
|
||||
<li>[win] Fix bug that some items of context menu in Windows Explorer don't show up</li>
|
||||
|
|
|
|||
|
|
@ -4538,6 +4538,15 @@
|
|||
</label>
|
||||
<ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#3015-20250626" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
3.0.15 (2025/06/26)
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#3014-20250507" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
|
@ -5300,6 +5309,15 @@
|
|||
</label>
|
||||
<ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#3015-20250626" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
3.0.15 (2025/06/26)
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#3014-20250507" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
|
@ -6040,6 +6058,15 @@
|
|||
|
||||
|
||||
<h1 id="seadrive-client-changelog">SeaDrive Client Changelog<a class="headerlink" href="#seadrive-client-changelog" title="Permanent link">¶</a></h1>
|
||||
<h3 id="3015-20250626">3.0.15 (2025/06/26)<a class="headerlink" href="#3015-20250626" title="Permanent link">¶</a></h3>
|
||||
<ul>
|
||||
<li>Persist file sync errors over restart</li>
|
||||
<li>Save encryption keys for encrypted libraries after delete confirmation "No"</li>
|
||||
<li>Increase fs-id-list request timeout to 30 minutes</li>
|
||||
<li>Update parent folder modification time when file are updated</li>
|
||||
<li>[mac] Fix memory leaks when removing downloaded items from cache</li>
|
||||
<li>[linux] Add Nautilus extension for GNOME</li>
|
||||
</ul>
|
||||
<h3 id="3014-20250507">3.0.14 (2025/05/07)<a class="headerlink" href="#3014-20250507" title="Permanent link">¶</a></h3>
|
||||
<ul>
|
||||
<li>[win] Avoid potential file overwriting issue after internal metadata is removed by Anti-virus</li>
|
||||
|
|
|
|||
|
|
@ -4481,6 +4481,15 @@
|
|||
<nav class="md-nav" aria-label="12.0">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#12014-2025-05-29" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
12.0.14 (2025-05-29)
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#12011-2025-03-19" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
|
@ -5510,6 +5519,15 @@
|
|||
<nav class="md-nav" aria-label="12.0">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#12014-2025-05-29" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
12.0.14 (2025-05-29)
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#12011-2025-03-19" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
|
@ -6444,6 +6462,14 @@
|
|||
<h2 id="120">12.0<a class="headerlink" href="#120" title="Permanent link">¶</a></h2>
|
||||
<p><strong>Upgrade</strong></p>
|
||||
<p>Please check our document for how to upgrade to <a href="../../upgrade/upgrade_notes_for_12.0.x/">12.0</a></p>
|
||||
<h3 id="12014-2025-05-29">12.0.14 (2025-05-29)<a class="headerlink" href="#12014-2025-05-29" title="Permanent link">¶</a></h3>
|
||||
<ul>
|
||||
<li>[fix] Fix two stored XSS issues (In rendering terms and conditions and in institution admin page)</li>
|
||||
<li>Add S/MIME support for emails</li>
|
||||
<li>[fix] Fix a UI bug in "share admin -> share links"</li>
|
||||
<li>[fix] Fix a bug in rendering "system admin -> users"</li>
|
||||
<li>Update translations</li>
|
||||
</ul>
|
||||
<h3 id="12011-2025-03-19">12.0.11 (2025-03-19)<a class="headerlink" href="#12011-2025-03-19" title="Permanent link">¶</a></h3>
|
||||
<ul>
|
||||
<li>[fix] Fix a stored XSS issue</li>
|
||||
|
|
|
|||
|
|
@ -4678,7 +4678,7 @@
|
|||
<span class="p">)</span>
|
||||
</code></pre></div>
|
||||
<div class="admonition tip">
|
||||
<p class="admonition-title">Please replease <code>+=</code> to <code>=</code> if <code>EXTRA_MIDDLEWARE_CLASSES</code> or <code>EXTRA_MIDDLEWARE</code> is not defined</p>
|
||||
<p class="admonition-title">Please replease <code>+=</code> to <code>=</code> if <code>EXTRA_MIDDLEWARE</code> is not defined</p>
|
||||
</div>
|
||||
<h2 id="add-institutions-and-institution-admins">Add institutions and institution admins<a class="headerlink" href="#add-institutions-and-institution-admins" title="Permanent link">¶</a></h2>
|
||||
<p>After restarting Seafile, a system admin can add institutions by adding institution name in admin panel. He can also click into an institution, which will list all users whose <code>profile.institution</code> match the name.</p>
|
||||
|
|
|
|||
|
|
@ -5127,6 +5127,10 @@ use_go_fileserver = true
|
|||
# The unit is in M. Default to 2G.
|
||||
fs_cache_limit = 100
|
||||
</code></pre></div>
|
||||
<p>Since Pro 12.0.10 version, you can set the max threads of fs-id-list requests. When you download a repo, Seafile client will request fs id list, and you can control the maximum concurrency for handling fs-id-list requests in the go fileserver through <code>fs_id_list_max_threads</code> configuration, which defaults to 10.
|
||||
<div class="highlight"><pre><span></span><code>[fileserver]
|
||||
fs_id_list_max_threads = 20
|
||||
</code></pre></div></p>
|
||||
<h2 id="profiling-go-fileserver-performance">Profiling Go Fileserver Performance<a class="headerlink" href="#profiling-go-fileserver-performance" title="Permanent link">¶</a></h2>
|
||||
<p>Since Seafile 9.0.7, you can enable the profile function of go fileserver by adding the following configuration options:</p>
|
||||
<div class="highlight"><pre><span></span><code># profile_password is required, change it for your need
|
||||
|
|
|
|||
|
|
@ -0,0 +1,22 @@
|
|||
services:
|
||||
|
||||
sdoc-server:
|
||||
image: seafileltd/sdoc-server:0.8.0
|
||||
container_name: sdoc-server
|
||||
ports:
|
||||
- 80:80
|
||||
# - 443:443
|
||||
# - 7070:7070
|
||||
# - 8888:8888
|
||||
volumes:
|
||||
- /opt/seadoc-data/:/shared
|
||||
environment:
|
||||
- DB_HOST=192.168.0.2
|
||||
- DB_PORT=3306
|
||||
- DB_USER=user
|
||||
- DB_PASSWD=password # Required, password of MySQL service.
|
||||
- DB_NAME=sdoc_db
|
||||
- TIME_ZONE=Etc/UTC # Optional, default is UTC. Should be uncomment and set to your local time zone.
|
||||
- SDOC_SERVER_LETSENCRYPT=false # Whether to use https or not.
|
||||
- SDOC_SERVER_HOSTNAME=sdoc-server.example.com # Specifies your host name if https is enabled.
|
||||
- SEAHUB_SERVICE_URL=http://seafile.example.com
|
||||
File diff suppressed because one or more lines are too long
|
|
@ -768,6 +768,19 @@
|
|||
|
||||
|
||||
|
||||
<label class="md-nav__link md-nav__link--active" for="__toc">
|
||||
|
||||
|
||||
|
||||
<span class="md-ellipsis">
|
||||
HTTPS and Caddy
|
||||
|
||||
</span>
|
||||
|
||||
|
||||
<span class="md-nav__icon md-icon"></span>
|
||||
</label>
|
||||
|
||||
<a href="./" class="md-nav__link md-nav__link--active">
|
||||
|
||||
|
||||
|
|
@ -780,6 +793,58 @@
|
|||
|
||||
</a>
|
||||
|
||||
|
||||
|
||||
<nav class="md-nav md-nav--secondary" aria-label="Table of contents">
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<label class="md-nav__title" for="__toc">
|
||||
<span class="md-nav__icon md-icon"></span>
|
||||
Table of contents
|
||||
</label>
|
||||
<ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#engage-https-by-caddy" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
Engage HTTPS by caddy
|
||||
</span>
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="Engage HTTPS by caddy">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#with-a-automatically-generated-certificate" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
With a automatically generated certificate
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#using-a-custom-existing-certificate" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
Using a custom (existing) certificate
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
|
||||
|
|
@ -4556,6 +4621,47 @@
|
|||
|
||||
|
||||
|
||||
<label class="md-nav__title" for="__toc">
|
||||
<span class="md-nav__icon md-icon"></span>
|
||||
Table of contents
|
||||
</label>
|
||||
<ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#engage-https-by-caddy" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
Engage HTTPS by caddy
|
||||
</span>
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="Engage HTTPS by caddy">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#with-a-automatically-generated-certificate" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
With a automatically generated certificate
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#using-a-custom-existing-certificate" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
Using a custom (existing) certificate
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
|
||||
</nav>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -4579,6 +4685,13 @@
|
|||
<p>From Seafile Docker 12.0, HTTPS will be handled by the <a href="https://caddyserver.com/docs/"><strong><em>Caddy</em></strong></a>. The default caddy image used of Seafile docker is <a href="https://github.com/lucaslorentz/caddy-docker-proxy"><code>lucaslorentz/caddy-docker-proxy:2.9-alpine</code></a>.</p>
|
||||
</div>
|
||||
<p>Caddy is a modern open source web server that mainly binds external traffic and internal services in <a href="../overview/">seafile docker</a>. In addition to the advantages of traditional proxy components (e.g., <em>nginx</em>), Caddy also makes it easier for users to complete the acquisition and update of HTTPS certificates by providing simpler configurations. </p>
|
||||
<h2 id="engage-https-by-caddy">Engage HTTPS by caddy<a class="headerlink" href="#engage-https-by-caddy" title="Permanent link">¶</a></h2>
|
||||
<p>We provide two options for enabling HTTPS via <em>Caddy</em>, which mainly rely on The caddy docker proxy container from <a href="https://github.com/lucaslorentz/caddy-docker-proxy">Lucaslorentz</a> supports dynamic configuration with labels:</p>
|
||||
<ul>
|
||||
<li>With a automatically generated certificate</li>
|
||||
<li>Using a custom (existing) certificate</li>
|
||||
</ul>
|
||||
<h3 id="with-a-automatically-generated-certificate">With a automatically generated certificate<a class="headerlink" href="#with-a-automatically-generated-certificate" title="Permanent link">¶</a></h3>
|
||||
<p>To engage HTTPS, users only needs to correctly configure the following fields in <code>.env</code>:</p>
|
||||
<div class="highlight"><pre><span></span><code><span class="nv">SEAFILE_SERVER_PROTOCOL</span><span class="o">=</span>https
|
||||
<span class="nv">SEAFILE_SERVER_HOSTNAME</span><span class="o">=</span>example.com
|
||||
|
|
@ -4586,6 +4699,42 @@
|
|||
<p>After Seafile Docker startup, you can use following command to access the logs of <em>Caddy</em></p>
|
||||
<div class="highlight"><pre><span></span><code>docker<span class="w"> </span>logs<span class="w"> </span>seafile-caddy<span class="w"> </span>-f
|
||||
</code></pre></div>
|
||||
<h3 id="using-a-custom-existing-certificate">Using a custom (existing) certificate<a class="headerlink" href="#using-a-custom-existing-certificate" title="Permanent link">¶</a></h3>
|
||||
<p>With the <code>caddy.yml</code>, a default volume-mount is created: <code>/opt/seafile-caddy</code> (as you can change it by modifying <code>SEAFILE_CADDY_VOLUME</code> in <code>.env</code>). By convention you should provide your certificate & key files in the container host filesystem under <code>/opt/seafile-caddy/certs/</code> to make it available to caddy:</p>
|
||||
<div class="highlight"><pre><span></span><code>/opt/seafile-caddy/certs/
|
||||
├──<span class="w"> </span>cert.pem<span class="w"> </span><span class="c1"># xxx.crt in some case</span>
|
||||
├──<span class="w"> </span>key.pem<span class="w"> </span><span class="c1"># xxx.key in some case</span>
|
||||
</code></pre></div>
|
||||
<div class="admonition tip">
|
||||
<p class="admonition-title">Command to generate custom certificates</p>
|
||||
<p>With this command, you can generate your own custom certificates:</p>
|
||||
<div class="highlight"><pre><span></span><code><span class="nb">cd</span><span class="w"> </span>/opt/seafile-caddy/certs
|
||||
openssl<span class="w"> </span>req<span class="w"> </span>-x509<span class="w"> </span>-nodes<span class="w"> </span>-days<span class="w"> </span><span class="m">365</span><span class="w"> </span>-newkey<span class="w"> </span>rsa:2048<span class="w"> </span>-keyout<span class="w"> </span>./key.pem<span class="w"> </span>-out<span class="w"> </span>./cert.pem
|
||||
</code></pre></div>
|
||||
<p><strong>Please be aware that custom certicates can not be used for ip-adresses</strong></p>
|
||||
</div>
|
||||
<p>Then modify <code>seafile-server.yml</code> to enable your custom certificate, by the way, we strongly recommend you to make a backup of <code>seafile-server.yml</code> before doing this:</p>
|
||||
<div class="highlight"><pre><span></span><code>cp<span class="w"> </span>seafile-server.yml<span class="w"> </span>seafile-server.yml.bak
|
||||
nano<span class="w"> </span>seafile-server.yml
|
||||
</code></pre></div>
|
||||
<p>and</p>
|
||||
<div class="highlight"><pre><span></span><code>services:
|
||||
...
|
||||
seafile:
|
||||
...
|
||||
volumes:
|
||||
...
|
||||
# If you use a self-generated certificate, please add it to the Seafile server trusted directory (i.e. remove the comment symbol below)
|
||||
# - "/opt/seafile-caddy/certs/cert.pem:/usr/local/share/ca-certificates/cert.crt"
|
||||
labels:
|
||||
caddy: ${SEAFILE_SERVER_HOSTNAME:?Variable is not set or empty} # leave this variables only
|
||||
caddy.tls: "/data/caddy/certs/cert.pem /data/caddy/certs/key.pem"
|
||||
...
|
||||
</code></pre></div>
|
||||
<div class="admonition warning">
|
||||
<p class="admonition-title">DNS resolution must work inside the container</p>
|
||||
<p>If you're using a <strong><em>non-public url</em></strong> like <code>my-custom-setup.local</code>, you have to make sure, that the docker container can resolve this DNS query. If you don't run your own DNS servers, you have to add extras_hosts to your <code>.yml</code> file.</p>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue