selfhost.directory

The index of self-hostable projects — ranked, categorized and served with live updates.
Own your data and stop giving it to big tech.

logpaste logo

Self-host logpaste

0.3.4

Minimalist log file upload and sharing service

ReleaseOpen SourceMIT
Updated7 months ago
LanguageGo
Setup difficultyEasy
Stars
341
Port
3001 (HTTP web server)
Docker
mtlynch/logpaste
Install with Docker
logpaste screenshot 1

What is logpaste?

LogPaste lets you upload and share debug logs through a web interface, command line, or JavaScript. It runs as a single Docker container using SQLite for storage, and can automatically back up data to any S3-compatible service or Google Cloud Storage using Litestream. The interface text (title, subtitle, footer) can be customized without code changes. Rate limiting and max upload size are configurable. Deployment guides cover fly.io, Heroku, Google Cloud Run, and Amazon LightSail.

logpaste alternatives

Should you self-host logpaste?

logpaste scores 49/100 on selfhost.directory (how scoring works) and ranks #83 of 166 in Developer Tools. It has 341 GitHub stars.

It shipped 3 stable releases in the past year. The latest, 0.3.4, came out on 30 March 2026.

Setup is easy: most people get it running in one sitting. An official Docker image is available. It is MIT-licensed and written mostly in Go.

Its closest alternative on selfhost.directory is openhands (87/100, 92 252 stars). It scores higher overall, so compare the two before you pick. See logpaste vs openhands side by side.

Features

  • Automatic data restore
  • Configurable max upload size
  • Customizable UI text
  • Google Cloud Storage replication
  • Log file upload via CLI
  • Log file upload via JavaScript
  • Rate Limiting
  • S3-compatible cloud storage replication
  • Single-Container Deployment
  • Web UI for log uploads

logpaste README

logpaste

CircleCI Docker Pulls License

A minimalist web service for uploading and sharing log files.

LogPaste animated demo

Features

How to install logpaste

Install logpaste with Docker

Environment variables
PORT, LP_BEHIND_PROXY, DB_REPLICA_URL, LITESTREAM_REGION, LITESTREAM_ACCESS_KEY_ID, LITESTREAM_SECRET_ACCESS_KEY

docker run
-e "PORT=3001"
-p 3001:3001/tcp
--volume "${PWD}/data:/app/data"
--name logpaste
mtlynch/logpaste

Mount a volume to persist the SQLite database

How to configure logpaste

  • PORT3001TCP port on which to listen for HTTP connections
  • LP_BEHIND_PROXYSet to 'y' if running behind an HTTP proxy to improve logging

    values: y

  • DB_REPLICA_URLS3 or GCS URL where you want to replicate the LogPaste datastore

    values: s3://bucket/db or gcs://bucket/db

  • LITESTREAM_REGIONAWS region where your S3 bucket is located
  • LITESTREAM_ACCESS_KEY_IDAWS access key ID for an IAM role with access to the bucket

logpaste releases & version history

More in Logging

Rate this project

Click to rate — no account needed.

0 comments

Posting as guest
Loading comments…