Files

T

EthanHealy01 f0a7f9af78 Collapse pymupdf-worker package into a single script

The pymupdf-worker/ directory existed only to register a pip entry point
for pymupdf-convert. Replace it with scripts/pymupdf_convert.py — a
standalone script installed directly onto PATH in the Dockerfile.

- Add scripts/pymupdf_convert.py (AGPL-3.0, same logic, shebang added)
- Update docker/base/Dockerfile to copy + install the script directly
  instead of pip-installing the package; remove now-redundant symlink
- Delete pymupdf-worker/ and its taskfile
- Update root LICENSE to reference the script file instead of directory

2026-06-02 00:48:55 +01:00

base

Collapse pymupdf-worker package into a single script

2026-06-02 00:48:55 +01:00

compose

Fix healthcheck in Docker files when SYSTEM_ROOTURIPATH is specified (#5954 )

2026-04-12 22:44:04 +01:00

embedded

Add server-side folders and files page UI (#6383 )

2026-05-27 12:52:46 +01:00

frontend

Restructure/frontend editor (#6404 )

2026-05-22 13:40:34 +01:00

unoserver

unoserver docker (#6328 )

2026-05-12 13:22:15 +01:00

README.md

Add Taskfile for unified dev workflow across all components (#6080 )

2026-04-15 14:16:57 +00:00

README.md

Docker Setup for Stirling-PDF

This directory contains the organized Docker configurations for the split frontend/backend architecture.

Using Taskfile (Recommended)

All Docker commands can be run from the project root using Task:

task docker:build            # Build standard image
task docker:build:fat        # Build fat image (all features)
task docker:build:ultra-lite # Build ultra-lite image
task docker:build:frontend   # Build frontend-only image
task docker:build:engine     # Build engine image
task docker:up               # Start standard compose stack
task docker:up:fat           # Start fat compose stack
task docker:up:ultra-lite    # Start ultra-lite compose stack
task docker:down             # Stop all running stacks
task docker:logs             # Tail compose logs

Directory Structure

docker/
├── backend/           # Backend Docker files
│   ├── Dockerfile            # Standard backend
│   ├── Dockerfile.ultra-lite # Minimal backend
│   └── Dockerfile.fat        # Full-featured backend
├── frontend/          # Frontend Docker files
│   ├── Dockerfile     # React/Vite frontend with nginx
│   ├── nginx.conf     # Nginx configuration
│   └── entrypoint.sh  # Dynamic backend URL setup
└── compose/           # Docker Compose files
    ├── docker-compose.yml           # Standard setup
    ├── docker-compose.ultra-lite.yml # Ultra-lite setup
    └── docker-compose.fat.yml       # Full-featured setup

Usage

Separate Containers (Recommended)

From the project root directory:

# Standard version
docker-compose -f docker/compose/docker-compose.yml up --build

# Ultra-lite version
docker-compose -f docker/compose/docker-compose.ultra-lite.yml up --build

# Fat version
docker-compose -f docker/compose/docker-compose.fat.yml up --build

Access Points

Frontend: http://localhost:3000
Backend API (debugging): http://localhost:8080 (TODO: Remove in production)
Backend API (via frontend): http://localhost:3000/api/*

Configuration

Backend URL: Set VITE_API_BASE_URL environment variable for custom backend locations
Custom Ports: Modify port mappings in docker-compose files
Memory Limits: Adjust memory limits per variant (2G ultra-lite, 4G standard, 6G fat)

Google Drive Integration

VITE_GOOGLE_DRIVE_CLIENT_ID: OAuth 2.0 Client ID
VITE_GOOGLE_DRIVE_API_KEY: Create New API
VITE_GOOGLE_DRIVE_APP_ID: This is your project number in the GoogleCloud Settings

Development vs Production

Development: Keep backend port 8080 exposed for debugging
Production: Remove backend port exposure, use only frontend proxy