Photo Archive
Platform for photographers and organizers that centralizes photo sessions, upload and image processing, and gives clients galleries accessible via a unique code, with an optional password and individual or ZIP download.

Core stack
The challenge
The central challenge was delivering a large number of event images in a simple client experience with no mandatory account, keeping the originals for download while also generating versions light enough for smooth gallery browsing. On the operational side, the photographer needed separate sessions, access codes, multi-file upload, and visibility into volume and accesses.
The solution
The solution separates the React interface from an Express API with MySQL persistence and local disk storage. Multer writes uploads directly to the originals directory, Sharp validates the files and generates thumbnails and gallery versions, and the metadata needed for navigation is persisted relationally. Sessions receive unique server-generated codes and can have a bcrypt password; the client gallery uses pagination, search, and preview, and originals can be downloaded individually or aggregated into a ZIP streamed with archiver. Administration is separated through JWT authentication and offers CRUD for sessions, upload, and statistics.
Notable complexity
Photo Archive is a web application built for the controlled delivery of event photos to clients. The administrator creates a session with a name, description, and event date, and the backend generates a unique eight-character code. The session can be activated or deactivated and can receive an additional password, stored as a bcrypt hash. The administrative interface shows the number of photos, stored volume, and recorded accesses, and allows copying the code or opening the gallery directly.
Upload is handled through Multer with direct disk storage. For each accepted image, Sharp validates the format and dimensions, reads basic technical metadata, and generates two derived versions: a square 300 × 300 thumbnail for listing and a gallery image of up to 1200 × 1200, progressive JPEG at quality 85. The original is kept separately, and MySQL persists the initial name, file paths, size, resolution, and upload timestamp. Processing is done sequentially within the upload request; the code introduces no queue workers or separate asynchronous batching.
The client reaches the gallery using the code received from the photographer or organizer. The page reads the session information, requests the password when the session is protected, and loads photos paginated at 20 per page. The gallery offers grid or list mode, search by filename, preview in a modal, and download of the original. A separate route builds a ZIP archive of all originals on demand using archiver and streams the response to the browser. Public accesses are logged with IP and user agent, and the same session/IP combination is not normally re-logged more than once per hour on the main gallery routes.
The frontend is a React 19 + Vite 7 + Tailwind CSS 4 SPA, with a light visual identity based on a blue–indigo–purple gradient, translucent white cards, and Lucide iconography. The Express backend runs separately on Node.js, uses a MySQL pool, JWT for administration, and a separate client flow available at the API level, while the documented deployment uses PM2 and Nginx on a HestiaCP VPS. The repository contains no GitHub Actions and no automated test suite; there is only a utility script for checking upload limits.
From a hardening perspective, the analyzed code has a few issues that need to be addressed before presenting the platform as a private photo repository: rate limiting is disabled on the server, there are fallbacks for the JWT secret and the admin password, and the repository contains TLS material that should not be versioned. In addition, session password protection is applied on the main paginated endpoint, but is not consistently checked across all public photo/search/recent/download endpoints. The seed presents the real functionality without turning these mechanisms into a claim of complete security.
Key results
- React application separated into public surfaces, client gallery, and administration panel
- Photo sessions with name, description, event date, active/inactive status, and a unique eight-character access code
- Optional per-session password, persisted as a bcrypt hash and required by the main gallery interface
- Multi-file upload with Multer, configured for up to 500 MB per file and up to 1000 files per request
- Image validation via Sharp for JPEG/JPG, PNG, WebP, and TIFF, rejecting images under 100 × 100 px
- Automatic generation of a 300 × 300 thumbnail and a gallery version of up to 1200 × 1200, keeping the original separate
- MySQL persistence for sessions, photos, administrators, and the access log
- Gallery paginated at 20 photos, with grid/list mode, preview, and resolution information
- Client-side search by the file's original name
- Individual download of originals and full session download as an on-demand generated ZIP archive
- Administrative dashboard with active sessions, total photos, recent accesses, and total session count
- Filtering and sorting sessions by status, name, date, event date, or photo count
- Logging of public accesses with session, code, IP, user agent, and timestamp
- Documented VPS deployment with Nginx as reverse proxy/static server and PM2 for the Node.js process
Related projects
- CreativeSys AutoA custom online store with simple and variable products, a dynamic catalog and filters, checkout, EuPlătesc payments, commercial documents, full administration, and a separate quoting flow for car paint.
- Ghici Cine (Guess Who)A multiplayer browser party game with private rooms, words submitted by participants, real-time synchronized turns, per-player filtered state, and reconnection to the active session.
- Vedete & Inițiale (Celebrities & Initials)A multiplayer web app for TOMAPAN (categories/initial-letter) rounds in private rooms, with an access code, configurable categories, a shared letter, a timer, scoring for unique or duplicate answers, and real-time synchronization between players.
Want something similar?
Start with the estimate wizard — answer a few questions and get a realistic price range and timeline.