How mcalec-dev/gdl-api works
gdl-api is an Express-backed gallery-dl file library: users browse and retrieve files, search the indexed collection, and can upload content; accounts, pools, statistics, and administration provide supporting product capabilities. The graph emphasizes API routing, filesystem indexing and metadata, search, and persistence, while retaining the documented UI and other major API branches. Several route implementations are not sampled, so links to their underlying behavior are omitted where evidence is unavailable.
Main entry points: index.js API router · server.js Express server · upsert.js File indexing · repository.js Search repository
Components 31
Web application
- Express server
server.js - API router
routes/api/index.js - Browser interface
public/js/index.js - Authentication
routes/api/auth - User account API
routes/api/user - Administration
routes/api/admin
File library
- File API
routes/api/files.js - Collection filesystem
- Directory listing
utils/file/listing.js - Filesystem sync
utils/file/sync.js - File indexing
utils/file/upsert.js - Media metadata
utils/image/metadata.js - Media processing
utils/image/resize.js - Download API
routes/api/download.js - Upload API
routes/api/upload.js
Persistence and indexing
- Search repository
utils/search/repository.js - File records
models/File.js - Directory records
models/Directory.js - Uploaded file store
utils/gridfsUtils.js - Redis cache
utils/db/redisClient.js - Statistics snapshots
utils/stats/snapshot.js - Session storage
utils/sessionStore.js
Library features
- Search API
routes/api/search.js - Search engine
utils/search/searchDatabase.js - Pools
routes/api/pool.js - Random files
routes/api/random.js - Statistics
routes/api/stats.js - Announcements
routes/api/user/announcements.js - Health check
routes/api/health.js
Other components
- Gallery user
- MongoDB
Connections 35
- Gallery user → Browser interface: uses
- Express server → API router: mounts routes
server.js - Express server → Browser interface: renders pages
server.js - API router → Authentication: mounts
routes/api/index.js - API router → User account API: mounts
routes/api/index.js - API router → Administration: mounts
routes/api/index.js - API router → File API: mounts
routes/api/index.js - API router → Download API: mounts
routes/api/index.js - API router → Upload API: mounts
routes/api/index.js - API router → Search API: mounts
routes/api/index.js - API router → Pools: mounts
routes/api/index.js - API router → Random files: mounts
routes/api/index.js - API router → Statistics: mounts
routes/api/index.js - API router → Announcements: mounts
routes/api/index.js - API router → Health check: mounts
routes/api/index.js - File API → Directory listing: uses
- Directory listing → Collection filesystem: reads
- Filesystem sync → Collection filesystem: scans
utils/file/sync.js - Filesystem sync → File indexing: indexes entries
utils/file/sync.js - File indexing → File records: writes
utils/file/upsert.js - File indexing → Directory records: writes
utils/file/upsert.js - File indexing → Media metadata: gets metadata
utils/file/upsert.js - Search API → Search engine: invokes
routes/api/search.js - Search engine → Search repository: fetches results
utils/search/searchDatabase.js - Search repository → File records: queries
utils/search/repository.js - Search repository → Directory records: queries
utils/search/repository.js - Upload API → Uploaded file store: stores content
- Uploaded file store → MongoDB: persists
- Express server → MongoDB: connects
server.js - Express server → Session storage: initializes
server.js - Session storage → Redis cache: uses when available
utils/sessionStore.js - Session storage → MongoDB: falls back to
utils/sessionStore.js - Express server → Redis cache: initializes cache
server.js - Statistics → Statistics snapshots: uses snapshots
- Statistics snapshots → File records: reads listing data