Nick/fuji-photo-processor
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Move photo paths from /volume2/photos to /volume1/data/photos

Browse Source 
Immich data share is on /volume1/data, so photos belong there too.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Nick Roodenrijs
2026-03-08 19:06:35 +01:00
parent 04ca39d2be
commit 2a2e51b1ae
3 changed files with 24 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
README.md
View File

@@ -7,7 +7,7 @@ Automatic photo processing pipeline for Fuji X-H2 photos: camera uploads via FTP
```
┌─────────────┐ FTPS ┌──────────────────┐ watchdog ┌─────────────┐
│ Fuji X-H2 │ ──────────→ │ Synology NAS │ ────────────→ │ Processor │
│ (camera) │ port 21 │ /volume2/photos/ │ polling │ container │
│ (camera) │ port 21 │ /volume1/data/photos/ │ polling │ container │
└─────────────┘ (TLS) │ incoming/ │ └──────┬──────┘
└──────────────────┘ │
│ resize + move
@@ -39,7 +39,7 @@ Automatic photo processing pipeline for Fuji X-H2 photos: camera uploads via FTP
2. Enable FTP service on port **21**
3. Enable **FTP SSL/TLS encryption** (FTPS)
4. Set passive port range: **50000-50100**
5. Create a dedicated user `fujiftp` with write access to `/volume2/photos/incoming`
5. Create a dedicated user `fujiftp` with write access to `/volume1/data/photos/incoming`
### 2. Camera Configuration (Fuji X-H2)
@@ -72,9 +72,9 @@ The deploy script will:
### 4. Immich Integration
1. In Immich, go to **Administration → External Libraries**
2. Add a new library with import path: `/volume2/photos/processed`
2. Add a new library with import path: `/volume1/data/photos/processed`
3. Set scan interval (e.g., every 15 minutes)
4. Mount `/volume2/photos/processed` into the Immich container as a read-only volume
4. Mount `/volume1/data/photos/processed` into the Immich container as a read-only volume
## Container Details
@@ -82,9 +82,9 @@ The deploy script will:
| Container Path | Host Path | Purpose |
|----------------|----------------------------------------|---------------------------|
| `/incoming` | `/volume2/photos/incoming` | FTP upload landing zone |
| `/originals` | `/volume2/photos/originals` | Full-resolution originals |
| `/processed` | `/volume2/photos/processed` | Resized copies for Immich |
| `/incoming` | `/volume1/data/photos/incoming` | FTP upload landing zone |
| `/originals` | `/volume1/data/photos/originals` | Full-resolution originals |
| `/processed` | `/volume1/data/photos/processed` | Resized copies for Immich |
| `/data` | `/volume2/docker/photo-processor/data` | SQLite tracking database |
### Environment Variables
@@ -108,7 +108,7 @@ ssh -i ../SynologyDocker/synology_ssh_key ssh@192.168.175.141 \
### Common Issues
- **Files not detected**: Check that the FTP user has write permissions to `/volume2/photos/incoming`. The processor uses polling (not inotify) so there may be up to a 30-second delay.
- **Files not detected**: Check that the FTP user has write permissions to `/volume1/data/photos/incoming`. The processor uses polling (not inotify) so there may be up to a 30-second delay.
- **Permission denied on originals/processed**: Ensure the directories exist and are writable. The deploy script creates them automatically.
- **Duplicate filenames**: The processor tracks files by filename in SQLite. If you re-upload a file with the same name, it will be skipped. Delete the entry from `/volume2/docker/photo-processor/data/processed.db` to reprocess.
- **Container keeps restarting**: Check logs for Python errors. Common cause: missing directories or permission issues on volume mounts.