• Published:

Background

On June 11, the original developer of AList, Xhofe, confirmed in the Alist News subscription channel that the project had been handed over to a company for operation. Going forward, Xhofe will help review the code in the open-source repository and make sure the release branch is built automatically through CI.

OpenList presents itself as a more trustworthy and sustainable open-source alternative to AList. Its stated purpose is to reduce the risk of future closed-source, black-box, or otherwise untrusted changes. The project is also working on replacing the original author’s closed-source API and removing links that are considered untrusted.

Deploying OpenList

Here is a Docker-based deployment example:

version: "3"
services:
  openlist:
    container_name: openlist
    image: "openlistteam/openlist:latest"
    restart: "unless-stopped"
    networks:
      - 1panel-network
    ports:
      - "127.0.0.1:5244:5244"
      - "127.0.0.1:5245:5245"
    volumes:
      - /data/docker/openlist/data:/opt/openlist/data
      - /data/docker/openlist/mnt:/mnt
      - /etc/localtime:/etc/localtime:ro
    environment:
      - PUID=0
      - PGID=0
      - UMASK=022

Migrating from AList

The migration can be done through AList’s built-in backup feature. Export the backup as a JSON file from AList, then import that JSON file into OpenList to restore the configuration.

For mounted directories, the mnt path can either be pointed to the existing directory used by the old container, or the original directory can be copied and then mounted into the new OpenList container.

Related Posts