dumbwareio/dumbdrop

Sponsored OSS

By DumbWareio

•Updated 8 months ago

A stupid simple file upload app. No read, only write.

Image
Databases & storage
2

100K+

dumbwareio/dumbdrop repository overview

⁠DumbDrop

A stupid simple file upload application that provides a clean, modern interface for dragging and dropping files. Built with Node.js and vanilla JavaScript.

DumbDrop

No auth (unless you want it now!), no storage, no nothing. Just a simple file uploader to drop dumb files into a dumb folder.

⁠Table of Contents

⁠Quick Start

⁠Option 1: Docker (For Dummies)
# Pull and run with one command
docker run -p 3000:3000 -v ./uploads:/app/uploads dumbwareio/dumbdrop:latest
  1. Go to http://localhost:3000⁠
  2. Upload a File - It'll show up in ./uploads
  3. Celebrate on how dumb easy this was
⁠Option 2: Docker Compose (For Dummies who like customizing)

Create a docker-compose.yml file:

services:
    dumbdrop:
        image: dumbwareio/dumbdrop:latest
        ports:
            - 3000:3000
        volumes:
            # Where your uploaded files will land
            - ./uploads:/app/uploads
        environment:
            # Explicitly set upload directory inside the container
            UPLOAD_DIR: /app/uploads
            # The title shown in the web interface
            DUMBDROP_TITLE: DumbDrop
            # Maximum file size in MB
            MAX_FILE_SIZE: 1024
            # Optional PIN protection (leave empty to disable)
            DUMBDROP_PIN: 123456
            # Upload without clicking button
            AUTO_UPLOAD: false
            # The base URL for the application
            # You must update this to the url you use to access your site
            BASE_URL: http://localhost:3000

Then run:

docker compose up -d
  1. Go to http://localhost:3000⁠
  2. Upload a File - It'll show up in ./uploads
  3. Rejoice in the glory of your dumb uploads

Note: The UPLOAD_DIR environment variable is now explicitly set to /app/uploads in the container. The Dockerfile only creates the uploads directory, not local_uploads. The host directory ./uploads is mounted to /app/uploads for persistent storage.

⁠Option 3: Running Locally (For Developers)

For local development setup, troubleshooting, and advanced usage, see the dedicated guide:

šŸ‘‰ Local Development Guide⁠

⁠Features

  • šŸš€ Drag and drop file uploads
  • šŸ“ Multiple file selection
  • šŸŽØ Clean, responsive UI with Dark Mode
  • šŸ“¦ Docker support with easy configuration
  • šŸ“‚ Directory upload support (maintains structure)
  • šŸ”’ Optional PIN protection
  • šŸ“± Mobile-friendly interface
  • šŸ”” Configurable notifications via Apprise
  • ⚔ Zero dependencies on client-side
  • šŸ›”ļø Built-in security features
  • šŸ’¾ Configurable file size limits
  • šŸŽÆ File extension filtering

⁠Configuration

⁠Environment Variables
VariableDescriptionDefaultRequired
PORTServer port3000No
BASE_URLBase URL for the applicationhttp://localhost:PORT⁠No
MAX_FILE_SIZEMaximum file size in MB1024No
DUMBDROP_PINPIN protection (4-10 digits)NoneNo
DUMBDROP_TITLESite title displayed in headerDumbDropNo
APPRISE_URLApprise URL for notificationsNoneNo
APPRISE_MESSAGENotification message templateNew file uploaded {filename} ({size}), Storage used {storage}No
APPRISE_SIZE_UNITSize unit for notifications (B, KB, MB, GB, TB, or Auto)AutoNo
AUTO_UPLOADEnable automatic upload on file selectionfalseNo
ALLOWED_EXTENSIONSComma-separated list of allowed file extensionsNoneNo
ALLOWED_IFRAME_ORIGINSComma-separated list of origins allowed to embed the app in an iframeNoneNo
UPLOAD_DIRDirectory for uploads (Docker/production; should be /app/uploads in container)None (see LOCAL_UPLOAD_DIR fallback)No
LOCAL_UPLOAD_DIRDirectory for uploads (local dev, fallback: './local_uploads')./local_uploadsNo
  • UPLOAD_DIR is used in Docker/production. If not set, LOCAL_UPLOAD_DIR is used for local development. If neither is set, the default is ./local_uploads.
  • Docker Note: The Dockerfile now only creates the uploads directory inside the container. The host's ./local_uploads is mounted to /app/uploads and should be managed on the host system.
  • BASE_URL: If you are deploying DumbDrop under a subpath (e.g., https://example.com/watchfolder/), you must set BASE_URL to the full path including the trailing slash (e.g., https://example.com/watchfolder/). All API and asset requests will be prefixed with this value. If you deploy at the root, use https://example.com/.
  • BASE_URL must end with a trailing slash. The app will fail to start if this is not the case.

See .env.example for a template and more details.

ALLOWED_IFRAME_ORIGINS

To allow this app to be embedded in an iframe on specific origins (such as Organizr), set the ALLOWED_IFRAME_ORIGINS environment variable. For example:

ALLOWED_IFRAME_ORIGINS=https://organizr.example.com,https://myportal.com
  • If not set, the app will only allow itself to be embedded in an iframe on the same origin (default security).
  • If set, the app will allow embedding in iframes on the specified origins and itself.
  • Security Note: Only add trusted origins. Allowing arbitrary origins can expose your app to clickjacking and other attacks.
File Extension Filtering

To restrict which file types can be uploaded, set the ALLOWED_EXTENSIONS environment variable. For example:

ALLOWED_EXTENSIONS=.jpg,.jpeg,.png,.pdf,.doc,.docx,.txt

If not set, all file extensions will be allowed.

Notification Setup
⁠Message Templates

The notification message supports the following placeholders:

  • {filename}: Name of the uploaded file
  • {size}: Size of the file (formatted according to APPRISE_SIZE_UNIT)
  • {storage}: Total size of all files in upload directory

Example message template:

APPRISE_MESSAGE: New file uploaded {filename} ({size}), Storage used {storage}

Size formatting examples:

  • Auto (default): Chooses nearest unit (e.g., "1.44MB", "256KB")
  • Fixed unit: Set APPRISE_SIZE_UNIT to B, KB, MB, GB, or TB

Both {size} and {storage} use the same formatting rules based on APPRISE_SIZE_UNIT.

⁠Notification Support
  • Integration with Apprise⁠ for flexible notifications
  • Support for all Apprise notification services
  • Customizable notification messages with filename templating
  • Optional - disabled if no APPRISE_URL is set

⁠Security

⁠Features
  • Variable-length PIN support (4-10 digits)
  • Constant-time PIN comparison
  • Input sanitization
  • Rate limiting
  • File extension filtering
  • No client-side PIN storage
  • Secure file handling

⁠Technical Details

⁠Stack
  • Backend: Node.js (>=20.0.0) with Express
  • Frontend: Vanilla JavaScript (ES6+)
  • Container: Docker with multi-stage builds
  • Security: Express security middleware
  • Upload: Chunked file handling via Multer
  • Notifications: Apprise integration
⁠Dependencies
  • express: Web framework
  • multer: File upload handling
  • apprise: Notification system
  • cors: Cross-origin resource sharing
  • dotenv: Environment configuration
  • express-rate-limit: Rate limiting

⁠Contributing

  1. Fork the repository
  2. Create your feature branch (git checkout -b feature/amazing-feature)
  3. Commit your changes using conventional commits
  4. Push to the branch (git push origin feature/amazing-feature)
  5. Open a Pull Request

See Local Development (Recommended Quick Start)⁠ for local setup and guidelines.


Made with ā¤ļø by DumbWare.io⁠

⁠Future Features

  • Camera Upload for Mobile

Tag summary

Content type

Image

Digest

sha256:8a377413d…

Size

82.1 MB

Last updated

8 months ago

docker pull dumbwareio/dumbdrop:sha-ff8f813f493e89c7da056e7a3101ce2ef48e3960

This week's pulls

Pulls:

6,088

Last week