majorfi/immich-stack Docker 镜像 - 轩辕镜像

Immich Stack

Automatically groups similar photos into stacks within the Immich photo management system.

Quick Start

bash
# Create a .env file
cat > .env << EOL
API_KEY=your_immich_api_key
API_URL=[***]
RUN_MODE=cron
CRON_INTERVAL=60
EOL

# Run with Docker (using Docker Hub)
docker run -d --name immich-stack --env-file .env -v ./logs:/app/logs majorfi/immich-stack:latest

# Or using GitHub Container Registry
docker run -d  --name immich-stack --env-file .env -v ./logs:/app/logs ghcr.io/majorfi/immich-stack:latest

Environment Variables

Docker Compose

yaml
version: "3.8"

services:
  immich-stack:
    container_name: immich_stack
    # Use Docker Hub image (recommended for Portainer)
    image: majorfi/immich-stack:latest
    # Or use GitHub Container Registry
    # image: ghcr.io/majorfi/immich-stack:latest
    environment:
      - API_KEY=${API_KEY}
      - API_URL=${API_URL:-[***]}
      - DRY_RUN=${DRY_RUN:-false}
      - RESET_STACKS=${RESET_STACKS:-false}
      - REPLACE_STACKS=${REPLACE_STACKS:-false}
      - PARENT_FILENAME_PROMOTE=${PARENT_FILENAME_PROMOTE:-edit}
      - PARENT_EXT_PROMOTE=${PARENT_EXT_PROMOTE:-.jpg,.dng}
      - WITH_ARCHIVED=${WITH_ARCHIVED:-false}
      - WITH_DELETED=${WITH_DELETED:-false}
      - RUN_MODE=${RUN_MODE:-once}
      - CRON_INTERVAL=${CRON_INTERVAL:-86400}
    volumes:
      - ./logs:/app/logs
    restart: on-failure

Development

bash
# Build locally
docker build -t immich-stack .

# Run locally
docker run -d \
  --name immich-stack \
  --env-file .env \
  -v ./logs:/app/logs \
  immich-stack

Immich Stack

Immich Stack is a Go CLI tool and library for automatically grouping ("stacking") similar photos in the Immich photo management system. It provides configurable, robust, and extensible logic for grouping, sorting, and managing photo stacks via the Immich API. This project is heavily inspired by immich-auto-stack.

---

Features

• Automatic Stacking: Groups similar photos into stacks based on filename, date, and custom criteria.
• Configurable Grouping: Supports custom grouping logic via environment variables and command-line flags.
• Parent/Child Promotion: Fine-grained control over which files are promoted as stack parents (by substring or extension).
• CLI Tool: Command-line interface for batch processing and automation.
• Safe Operations: Supports dry-run mode, stack replacement, and reset with user confirmation.
• Comprehensive Logging: Colorful, structured logs for all operations.
• Tested and Modular: Table-driven tests, modular helpers, and clear separation of concerns.

---

Installation

Prerequisites

• Go (version 1.21 or later)
• Git

From Source

1. Clone the repository:

   sh
   git clone [***]
   cd immich-stack
   

2. Build the binary:

   sh
   go build -o immich-stack ./cmd/main.go
   

3. Move the binary to your PATH (optional):

   sh
   sudo mv immich-stack /usr/local/bin/
   

Using Pre-built Binaries

1. Download the latest release from the Releases page
2. Extract the archive
3. Move the binary to your PATH (optional)

Docker Installation

1. Clone the repository:

   sh
   git clone [***]
   cd immich-stack
   

2. Create a .env file from the example:

   sh
   cp .env.example .env
   

3. Edit the .env file with your Immich credentials and preferences:

   sh
   # Required
   API_KEY=your_immich_api_key
   API_URL=[***]
   
   # Optional - Default values shown
   DRY_RUN=false
   RESET_STACKS=false
   REPLACE_STACKS=false
   PARENT_FILENAME_PROMOTE=edit
   PARENT_EXT_PROMOTE=.jpg,.dng
   WITH_ARCHIVED=false
   WITH_DELETED=false
   
   # Run mode settings
   RUN_MODE=once  # Options: once, cron
   CRON_INTERVAL=86400  # in seconds, only used if RUN_MODE=cron
   

4. Start the service:

   sh
   docker compose up -d
   

5. To run in cron mode, set RUN_MODE=cron in your .env file and restart:

   sh
   docker compose down
   docker compose up -d
   

6. To view logs:

   sh
   docker compose logs -f
   

7. To stop the service:

   sh
   docker compose down
   

Integration with Immich Docker Compose

To integrate with an existing Immich installation:

1. Copy the immich-stack service from our docker-compose.yml into your Immich's docker-compose.yml

2. Add these environment variables to your Immich's .env file (you can also add the optional ones):

   sh
   # Immich Stack settings
   API_KEY=your_immich_api_key
   API_URL=[***]  # Use internal Docker network
   RUN_MODE=once  # Options: once, cron
   CRON_INTERVAL=86400  # in seconds, only used if RUN_MODE=cron
   

3. Add the service dependency in Immich's docker-compose.yml:

   yaml
   immich-stack:
     container_name: immich_stack
     image: ghcr.io/majorfi/immich-stack:latest
     environment:
       - API_KEY=${API_KEY}
       - API_URL=${API_URL:-[***]}
       - DRY_RUN=${DRY_RUN:-false}
       - RESET_STACKS=${RESET_STACKS:-false}
       - REPLACE_STACKS=${REPLACE_STACKS:-false}
       - PARENT_FILENAME_PROMOTE=${PARENT_FILENAME_PROMOTE:-edit}
       - PARENT_EXT_PROMOTE=${PARENT_EXT_PROMOTE:-.jpg,.dng}
       - WITH_ARCHIVED=${WITH_ARCHIVED:-false}
       - WITH_DELETED=${WITH_DELETED:-false}
       - RUN_MODE=${RUN_MODE:-once}
       - CRON_INTERVAL=${CRON_INTERVAL:-86400}
     volumes:
       - ./logs:/app/logs
     restart: on-failure
     depends_on:
       immich-server:
         condition: service_healthy
   

4. Restart your Immich stack:

   sh
   docker compose down
   docker compose up -d
   

Running

1. Create a .env file in your working directory with your Immich credentials:

   sh
   API_KEY=your_immich_api_key
   API_URL=[***]
   

2. Run the stacker:

   sh
   # Using the binary
   ./immich-stack
   
   # Or if installed in PATH
   immich-stack
   

3. Optional: Configure additional options via environment variables or flags:

   sh
   # Example with flags
   ./immich-stack --dry-run --parent-filename-promote=edit --parent-ext-promote=.jpg,.dng --with-archived --with-deleted
   
   # Or using environment variables
   export DRY_RUN=true
   export PARENT_FILENAME_PROMOTE=edit
   export PARENT_EXT_PROMOTE=.jpg,.dng
   export WITH_ARCHIVED=true
   export WITH_DELETED=true
   ./immich-stack
   

---

Directory Structure

immich-auto-stack/
├── cmd/                # CLI entrypoint (main.go)
├── pkg/
│   ├── stacker/        # Stacking logic, types, and tests
│   ├── immich/         # Immich API client and integration
│   └── utils/          # Utility helpers and logging

---

CLI Usage

The main entrypoint is cmd/main.go, which provides a Cobra-based CLI:

sh
go run ./cmd/main.go --api-key <API_KEY> --api-url <API_URL> [flags]

Flags and Environment Variables

• Flags take precedence over environment variables.
• If --reset-stacks is set, user confirmation is required.

---

Stacking Logic

Grouping

• Default Criteria: Groups by base filename (before extension) and local capture time.
• Custom Criteria: Override with the --criteria flag or CRITERIA environment variable.

Sorting

• Parent Promotion: Use --parent-filename-promote or PARENT_FILENAME_PROMOTE (comma-separated substrings) to promote files as stack parents.
• Extension Promotion: Use --parent-ext-promote or PARENT_EXT_PROMOTE (comma-separated extensions) to further prioritize.
• Extension Rank: Built-in priority: .jpeg > .jpg > .png > others.
• Alphabetical: Final tiebreaker.

Example

For files: L***.JPG, L***.edit.jpg, L***.DNG With PARENT_FILENAME_PROMOTE=edit and PARENT_EXT_PROMOTE=.jpg,.dng in your .env file, or with --parent-filename-promote=edit and --parent-ext-promote=.jpg,.dng, the order will be:

L***.edit.jpg
L***.JPG
L***.DNG

---

Library Structure

pkg/stacker

• StackBy: Groups assets into stacks and sorts them based on promotion rules.
• SortStack: Sorts assets in a stack by promotion and extension rules.
• Types: Asset, Stack, Criteria, etc.

pkg/immich

• Client: Handles all Immich API interactions (fetch, modify, delete stacks/assets).
• FetchAllStacks: Retrieves all stacks, with reset and cleanup logic.
• FetchAssets: Retrieves all assets, paginated.
• ModifyStack/DeleteStack: Stack management.
• ListDuplicates: Finds and logs duplicate assets.

pkg/utils

• helper.go: Array comparison, string cleaning.
• logs.go: Colorful, structured logging helpers (info, error, debug, pretty-print).

---

Example Workflow

1. Fetch all stacks and assets from Immich.
2. Group assets into stacks using criteria.
3. Sort each stack to determine the parent and children.
4. Apply changes via the Immich API (create, update, or delete stacks as needed).
5. Log all actions and optionally run in dry-run mode for safety.

---

Testing

• Table-driven tests for all major logic in pkg/stacker/stacker_test.go and pkg/immich/client_test.go.
• Run with:

  sh
  go test ./pkg/...
  

---

Extending

• Custom Grouping: Edit or override criteria via command-line flags or environment variables.
• Custom Promotion: Set --parent-filename-promote and/or --parent-ext-promote for your workflow.
• API Integration: Extend pkg/immich/client.go for new Immich endpoints.

---

Contributing

• Follow the code style and comment conventions (see code for examples).
• Add tests for new features.
• Document all exported functions and types.

---

License

MIT