OpenList Archive 项目预览

Overview

What
为公开资源提供目录、预览与下载入口,并由我独立运营这个 OpenList 实例。
Why
把文件目录和存储提供者的生命周期从 Kita 内容系统中分离出来。
Boundary
这里记录的是部署实例,不是自研 OpenList 源码;Kita 不调用其 API,也不共享数据库或 volume。
Type
Independent service
Period
2026 — Present
Operator
Kral
Upstream
OpenListTeam
Application
OpenList official image
Runtime
Docker · Coolify
State
Independent data volume
Storage
Provider-managed file sources
Contract
Public HTTPS URL
Service boundaries

Architecture

01
Client
Browser → OpenList service boundary

Directory · preview · download

02
OpenList service boundary
OpenList · OpenList Admin

Application: Official image · public UI / Administration: Providers · users · configuration

03
Persistent dependencies
Data volume · Storage providers

Application state: Configuration · service state / File sources: Independent credentials and lifecycle

04
Runtime / deployment
Docker · Coolify
05
URL-only relation
Kita Games

Stores a public archive URL · no shared database or startup dependency

Service operation

Run the archive service

This record describes an operated OpenList instance, not a fork of the upstream application. Deployment uses the official image and keeps its state outside Kita.

Image
OpenList official image
Runtime
Docker · Coolify
State
Persistent data volume
Access
archive.kral-koharu.com

Rebuild sequence

  1. Deploy the upstream applicationUse the official OpenList image as an independent Docker or Coolify application.
  2. Attach persistent stateKeep the OpenList data volume outside Kita and include it in the service backup boundary.
  3. Configure the instanceCreate the administrator and storage providers through OpenList Admin; credentials stay inside this service.
  4. Publish and verify the URLhttps://archive.kral-koharu.com/Confirm directory browsing, preview and download without depending on Kita startup.

Verification

Public service
The HTTPS directory should work independently of Kita.
archive.kral-koharu.com
Boundary
Kita stores a public link and does not call the OpenList API.
URL-only relation
Service boundary

Configuration surface

Provider credentials and runtime state belong to OpenList. They are deliberately not shared with Kita, PostgreSQL or Payload.

Key files and surfaces

Administration
OpenList Admin
State
Application data volume
Storage
Provider-managed file sources
Relation
Public URL only
ParameterSource / scopeRequirementEffect
Application image
Source: Coolify / Docker
Scope: Runtime
Requirement · RequiredApply · RedeploySelects the upstream OpenList release used by the service.
Data volume
Source: Runtime configuration
Scope: State
Requirement · RequiredApply · Redeploy and verify backupPersists application configuration and service state.
Storage providers
Source: OpenList Admin
Scope: Service
Requirement · RequiredValue · SecretApply · Runtime configurationDefines the file sources exposed by the directory.
Public URL
Source: DNS · Coolify
Scope: Relation
Requirement · RequiredApply · DNS / redeployProvides the only formal link stored by Kita.
Project history

Evolution

2026.07 — Current
  • Integration
    Games begins storing public archive URLs

    OpenList remains outside Kita Compose and shares no database.

  • Decision
    The URL-only application boundary is documented

    API integration and a custom frontend fork are deliberately rejected.

  • Active
    The independent service remains online

    Storage-provider choice and complete data-volume recovery remain explicit operating work.

Event log

Project Activity