Moving from Palmr.

What moves with you

• Database. On its first start Amfora renames prisma/palmr.db to prisma/amfora.db, once, with its WAL files. Users, shares, receive links and settings stay as they were.
• Files in bundled storage. An existing bucket is kept when you do not set MINIO_BUCKET, so every uploaded file stays where it is.
• Links you already sent. Same paths, same ports (5487 for the web interface, 9379 for bundled storage), so a link in someone's inbox keeps working.
• External S3. The ENABLE_S3 and S3_* variables are the same; nothing to change.

Five steps

1. Back up. Stop Palmr and copy the whole data volume, or take a snapshot. docker compose stop, then back up the directory or volume mounted at /app/server.
2. Swap the image. In your compose file replace the Palmr image with ghcr.io/solutionmax/amfora:2.2.0. Keep the volume line exactly as it is.
3. Rename the settings that carried the Palmr name, see below.
4. Start. docker compose up -d, then docker compose logs -f until you see the database migration and "Starting Amfora Application".
5. Check. Sign in with your existing account, open a share you sent before and download a file from it.

services:
  amfora:
    image: ghcr.io/solutionmax/amfora:2.2.0   # was: kyantech/palmr
    ports:
      - "5487:5487"
      - "9379:9379"
    volumes:
      - palmr_data:/app/server                # unchanged
    environment:
      APP_URL: "https://files.example.com"
      STORAGE_URL: "https://storage.example.com"
volumes:
  palmr_data:                                 # same block as in your Palmr file

Run it from the same directory as before, so Compose finds the same project and volume names.

Settings to rename

• PALMR_UID and PALMR_GID become AMFORA_UID and AMFORA_GID. Without them the container runs as uid 1001; set them to the owner of your existing files to avoid a long ownership change on the first start.
• The container name in examples is amfora; rename yours if scripts refer to it.
• Branding is now set in the admin area under Customization and stored on the server, so every visitor sees the same name, logo and colour.

Going back

Amfora 2 adds tables and settings to the database, so the way back is the backup from step 1, not the new volume. Restore it and start the Palmr image again.

After the move

• Updates: pull a new tag, or set up signed over the air updates once and install them from the admin area.
• Your own brand without the "Powered by Amfora" credit on public pages: the brandpack.
• Something not carried over? Mail [email protected]; it is a bug we want to hear about.