How to set up Rustypaste with Docker for self-hosting?

Use the provided Docker image with volume mounts for the upload directory and config.toml, and set environment variables like AUTH_TOKEN. The README includes a detailed docker run command and docker-compose.yml example for quick deployment.

Can Rustypaste handle large file uploads?

Yes, but you need to configure the server and reverse proxy (e.g., Nginx) to increase client_max_body_size, as shown in the Nginx snippet. Otherwise, you may encounter 413 errors for larger files.

Rustypaste vs privatebin: which is better for secure code snippets?

Rustypaste is simpler and focuses on file uploads with expiration, while privatebin offers client-side encryption and more privacy features. Choose Rustypaste for ease of use and privatebin for enhanced security.

Does Rustypaste support user accounts or teams?

No, it only supports basic HTTP authentication with tokens, so there's no built-in user management, multi-user roles, or team collaboration features.

How to automate deletion of expired files in Rustypaste?

Enable the delete_expired_files setting in config.toml for automatic cleanup at intervals, or use the provided cron script to manually remove expired files based on timestamps.

Is there a web UI for Rustypaste or do I need to use curl?

No built-in web UI; you must configure an HTML form as per the examples, or rely on third-party clients like ShareX or rustypaste-ui for a graphical interface beyond CLI usage.

Open-Awesome

rustypaste

MITRustv0.16.1Self-Hosted

A minimal, self-hosted file upload and pastebin service written in Rust.

Visit Website GitHub

1.2k stars78 forks0 contributors

What is rustypaste?

Rustypaste is a minimal file upload and pastebin service written in Rust. It allows users to upload files or text snippets and generate shareable URLs, with features like expiration, one-shot links, and URL shortening. It solves the need for a simple, self-hosted alternative to cloud-based pastebin and file-sharing services.

Target Audience

Developers and sysadmins who need a lightweight, self-hosted solution for sharing files or code snippets internally or publicly.

Value Proposition

Developers choose Rustypaste for its simplicity, performance (thanks to Rust), and ease of deployment without external dependencies like a database. Its focus on self-hosting and minimal configuration makes it ideal for private or controlled environments.

Overview

A minimal file upload/pastebin service.

Use Cases

Best For

Self-hosting a private pastebin for team code snippets
Quickly sharing files via CLI with expiration controls
Setting up a lightweight URL shortener for internal use
Deploying a file upload service without database setup
Creating one-time share links for sensitive documents
Building a simple file hosting service with Docker

Not Ideal For

Projects requiring user accounts and granular access controls
High-traffic public services with millions of uploads
Teams needing built-in web UI or real-time collaboration features
Environments where file metadata search or advanced analytics are essential

Pros & Cons

Pros

Minimal Deployment Overhead

Available as a single binary, Docker image, or via package managers, making installation and setup straightforward without complex dependencies.

Filesystem Simplicity

Uses the local filesystem for storage, eliminating the need for databases and reducing maintenance complexity for small-scale deployments.

Flexible Sharing Features

Supports expiring links, one-shot views, URL shortening, and remote URL fetching, covering common pastebin and file-sharing use cases.

Performance and Reliability

Written in Rust, it leverages the language's efficiency for fast handling of uploads and requests, ideal for resource-constrained self-hosting.

Cons

Scalability Bottlenecks

Filesystem storage can become inefficient for large volumes of files or high concurrency, as admitted by the reliance on manual cleanup scripts and lack of distributed support.

Basic Security Model

Only offers HTTP basic authentication and token-based deletion, missing modern features like OAuth, encryption at rest, or audit logs, which limits enterprise use.

No Native Web Interface

Requires custom HTML configuration or third-party clients for a graphical UI, adding overhead for user-friendly deployments compared to turnkey solutions.

Frequently Asked Questions

Related Projects

Pingora

A library for building fast, reliable and evolvable network services.

🌟 For when you really just want to serve some files over HTTP right now!

Stars7,574

Forks376

Last commit14 hours ago

simple-http-server

Simple http server in Rust (Windows/Mac/Linux)

Stars3,409

Forks217

Last commit1 month ago

Yopass

Secure sharing of secrets, passwords and files

Stars2,751

Forks400

Last commit2 days ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub