← Back to all sparks
S

Seafile

COLLAB
Velocity2.5

Self-hosted file sync and share platform

Seafile's server repo ships small hardening fixes across three branches at once.

file-syncself-hosteddata-integritymaintenancestorage
◆Current state
The seafile-server repo tags fixes on the 14.0 and 13.0 lines and on SeaTable builds. The same commit is often tagged on several versions at once. Recent work is defensive: validating file-system object sizes, testing garbage collection under concurrent uploads, and checking errors on file copy. The one configuration change is support for a SEAFILE_DATA_DIR environment variable.
◆Where it's heading
The server core is in steady maintenance, with fixes backported across 13.0, 14.0 and SeaTable. The focus is data-integrity robustness rather than new capability.
◆Prediction
Expect more 14.0.x patch tags with integrity and GC fixes; nothing in the entries points to new features.

◆Recent moves

  1. 20d ago

    v14.0.9: Validate file-system object size

    Validates the file-system object content size and fixes its integer type. A small integrity hardening on the 14.0 line.

    View source ↗
  2. 1mo ago

    v14.0.8: GC tests under concurrent upload

    Adds tests for garbage collection during concurrent uploads, plus CI and Go security fixes. Mostly test coverage, aimed at the data-loss edge case GC can hit.

    View source ↗
  3. 4mo ago

    v13.0.25: Check errors on file copy

    The same copy-error fix tagged on an earlier 13.0 version. A duplicate tag rather than a separate change.

    View source ↗
  4. 4mo ago

    SeaTable 6.2.0: Check errors on file copy

    The copy-error fix carried into the SeaTable 6.2.0 server build. It shows SeaTable shares this server core.

    View source ↗
  5. 4mo ago

    v13.0.28: Check errors on file copy

    Error checking on file copy, tagged on the 13.0 line. The same commit was tagged on two other versions the same day.

    View source ↗
  6. 7mo ago

    v13.0.22: Read data directory from SEAFILE_DATA_DIR

    The server now reads its data directory from SEAFILE_DATA_DIR instead of SEAFILE_CONF_DIR. A small but real deployment option for container setups, tagged across several 13.0 versions.

    View source ↗