How dnguyenminh/chunk-upload works
Project type and purpose
• This is a Java-based, multi-module Gradle project implementing a resumable “chunked” file upload service.
• It consists of three modules:
• server: a Spring Boot REST API for initializing uploads, accepting chunks, tracking progress, and assembling files on disk.
• client: a standalone Java client library (and CLI wrappers) that invokes the server’s REST endpoints.
• model: a shared DTO module (InitRequest, InitResponse) used by both client and server.
File structure
• Root: settings.gradle, build.gradle (common Gradle configuration & dependency management via Spring Boot BOM).
• server/: Spring Boot application code (controllers, services, managers, configuration), resources (application.properties, logback.xml), an embedded H2 file (used for tests), scripts for running & user setup.
• client/: Java client code invoking upload/init, upload/chunk, status, delete operations; build scripts; a local H2 file for testing.
• model/: simple DTOs with no external dependencies.
• Shared scripts/workflows: GitHub Actions for build/release, Qodana for code quality.
README for additional insights
• Clarifies REST API endpoints (/api/upload/init, /chunk, /status, DELETE).
• Storage is filesystem-based (“in-progress” & “complete” directories), no external database in production.
• Logging with SLF4J + Logback.