XTemp File Hub

XTemp File Hub is a lightweight temporary file sharing service, similar in spirit to bashupload: simple upload, direct download URL, and quick cleanup. It is also similar to transfer.sh, with a focus on simple self-hosted temporary file transfer workflows.

Features

• Drag & drop or click to upload files
• Download, copy link, or delete your file after upload
• Command line (curl) upload supported
• Native support for both curl raw PUT upload and multipart POST upload
• All file types supported (max size configurable)
• Configurable retention and cleanup interval via seconds-based backend config
• Built-in cleanup worker for both local storage and Cloudflare R2
• Crash-safe cleanup model: expiration is determined by filesystem/object timestamps, not in-memory queues

Usage

Web Interface

1. Open the website in your browser.
2. Read and accept the terms by typing ACCEPT.
3. Drag & drop a file or click the upload area to select a file.
4. Click Start Upload.
5. After upload, use the Download, Copy Link, or Delete File buttons as needed.
6. Click Return to Home to upload another file.

Command Line Example

You can upload files using curl:

# Method 1: Simple PUT
curl -T example.txt http://your-server.com

# Method 2: Multipart POST
curl -X POST -F "file=@example.txt" http://your-server.com/

After upload, you will receive a download link in the response.

To delete a file (replace <file_url> with your actual file link):

curl -X DELETE <file_url>

How to Run

Recommendation: For secure HTTPS access, it is highly recommended to deploy your own Nginx or another reverse proxy service in front of this application to handle TLS termination and SSL certificate management. The reverse proxy should forward external HTTPS traffic to the application. This setup improves security, compatibility, and allows you to manage certificates easily.

1. Local Storage (default, easy to start)

docker run -d -p 5000:5000 \
  -e MAX_UPLOAD_SIZE=524288000 \
  -e STORAGE_TYPE=local \
  -e XTEMP_STORAGE_PATH=/tmp \
  -e XTEMP_CONFIG_API_PASSWORD=your-strong-password \
  --name xtemp-app \
  evanshawn/xtemp:3.1

2. Cloudflare R2 Storage (recommended for production)

docker run -d -p 5000:5000 \
  -e MAX_UPLOAD_SIZE=524288000 \
  -e STORAGE_TYPE=r2 \
  -e R2_ACCOUNT_ID=your_account_id \
  -e R2_ACCESS_KEY_ID=your_access_key_id \
  -e R2_SECRET_ACCESS_KEY=your_secret_access_key \
  -e R2_BUCKET_NAME=your_backet_name \
  -e XTEMP_CONFIG_API_PASSWORD=your-strong-password \
  --name xtemp-app \
  evanshawn/xtemp:3.1

⚠️ Please replace your_account_id, your_access_key_id, your_secret_access_key, your_backet_name, and your-strong-password with your actual Cloudflare R2 information and a strong password.

Runtime Configuration

Max Upload Size

You can change the maximum allowed upload size without restarting the service by calling the following API:

1. Call the API to update max upload size
   Use a GET request with the correct password and new size (in bytes):

   curl "http://your-server.com/config/set_max_upload_size?password=your-strong-password&size=104857600"

   This will set the max upload size to 100MB.

2. Note:

   • The API is only available if XTEMP_CONFIG_API_PASSWORD is set.
   • Always use a strong password for this environment variable.

Environment example:

-e MAX_UPLOAD_SIZE=524288000 \
-e XTEMP_CONFIG_API_PASSWORD=your-strong-password

File Retention and Expiration

• XTEMP_RETENTION_SECONDS: file retention window in seconds (default: 86400, i.e. 24 hours).
• XTEMP_CLEANUP_INTERVAL_SECONDS: cleanup task interval in seconds (default: 3600, i.e. 1 hour).
• STORAGE_TYPE=local: expired files are removed automatically by the server cleanup task.
• STORAGE_TYPE=r2: expired objects are listed and deleted by the same server cleanup task via R2 DeleteObject.
• The DELETE API remains available for manual cleanup of specific files.
• Frontend terms read retention policy from backend instead of a hardcoded value.

Environment example:

-e XTEMP_RETENTION_SECONDS=86400 \
-e XTEMP_CLEANUP_INTERVAL_SECONDS=3600

Troubleshooting

• Files are not cleaned up:
  • Check XTEMP_RETENTION_SECONDS and XTEMP_CLEANUP_INTERVAL_SECONDS.
  • Confirm container time is correct (date inside container/host).
  • Check service logs for cleanup entries and deletion errors.
• R2 objects are not deleted:
  • Confirm R2_ACCOUNT_ID, R2_ACCESS_KEY_ID, R2_SECRET_ACCESS_KEY, R2_BUCKET_NAME are correct.
  • Confirm the key has permission to list and delete objects.

The demo site at xtemp.motofans.club is an example deployment.

License

MIT