# Send (Firefox Send)

> Simple private file sharing with encryption.

- Category: Storage & Backup
- Difficulty: intermediate
- Components: send, redis
- Tags: send, sharing, encrypted, temporary
- Source: https://docker.recipes/storage/send

## Overview

Send is a fork of Mozilla's discontinued Firefox Send service, providing secure temporary file sharing with client-side encryption. This implementation uses end-to-end encryption where files are encrypted in the browser before upload, ensuring that even the server never has access to unencrypted content. Users can set expiration limits based on time duration or download count, making it ideal for sharing sensitive documents that shouldn't persist indefinitely.

This Docker stack combines Send with Redis to provide a complete file sharing platform. Redis serves as the backend data store for managing file metadata, download counters, expiration tracking, and user sessions. The combination ensures fast lookup times for file information while maintaining the temporary nature of shared files through Redis's built-in expiration capabilities.

This configuration suits organizations needing secure internal file sharing, developers requiring temporary asset distribution, and privacy-conscious teams who want control over their file sharing infrastructure. Unlike cloud-based alternatives, this self-hosted approach keeps all file metadata and encrypted content within your infrastructure, providing complete data sovereignty while maintaining the convenience of web-based file sharing.

## Features

- Client-side AES-128-GCM encryption before upload ensures server-side privacy
- Configurable file expiration by download count and time limits
- Redis-backed metadata storage for fast file lookup and session management
- Support for ffsend CLI client enabling command-line file sharing workflows
- Configurable maximum file size limits via MAX_FILE_SIZE environment variable
- One-time download URLs that automatically expire after access
- Browser-based interface requiring no client software installation
- Automatic cleanup of expired files and associated Redis metadata

## Use cases

- Secure document sharing between legal teams with automatic expiration
- Temporary distribution of software builds and deployment artifacts
- Privacy-focused file sharing for healthcare organizations handling sensitive data
- Internal corporate file sharing avoiding external cloud services
- Developer collaboration for sharing logs, configs, and debug information
- Educational institutions distributing assignment materials with access limits
- Homelab enthusiasts creating personal secure file sharing for family use

## Prerequisites

- Docker host with minimum 640MB RAM (512MB for Redis, 128MB for Send)
- Port 1234 available for Send web interface access
- Understanding of Redis data persistence implications for file metadata
- Basic knowledge of environment variable configuration for file size limits
- Network access planning for users accessing the web interface

## docker-compose.yml

```yaml
services:
  send:
    image: registry.gitlab.com/timvisee/send:latest
    container_name: send
    restart: unless-stopped
    environment:
      REDIS_HOST: redis
      FILE_DIR: /uploads
    volumes:
      - send_uploads:/uploads
    ports:
      - "1234:1234"
    depends_on:
      - redis
    networks:
      - send

  redis:
    image: redis:alpine
    container_name: send-redis
    restart: unless-stopped
    networks:
      - send

volumes:
  send_uploads:

networks:
  send:
    driver: bridge
```

## .env

```bash
# Files auto-expire after download
```

## Usage notes

- Docs: https://github.com/timvisee/send#readme
- Access at http://localhost:1234 - Firefox Send fork
- End-to-end encryption in browser before upload
- Set expiration: time limit and/or download count
- Max file size configurable via MAX_FILE_SIZE env var
- CLI client: ffsend (pip install ffsend)

## Troubleshooting

- Upload fails with large files: Increase MAX_FILE_SIZE environment variable and check available disk space in send_uploads volume
- Redis connection errors in Send logs: Verify redis container is running and accessible via 'send' network, check Redis container logs
- Files not expiring automatically: Confirm Redis container has sufficient memory and isn't evicting keys, check Redis maxmemory-policy setting
- Browser encryption errors: Clear browser cache and cookies, ensure JavaScript is enabled for client-side encryption
- Download links not working: Check Redis key expiration settings and verify file still exists in uploads volume
- Send container fails to start: Verify /uploads directory permissions and ensure send_uploads volume is properly mounted

