Snipo
★ 73About
Community Ratings
No ratings yetNew this week
Read recap →Features
- snippet management
- single-user access
- master password protection
- terminal client
- VS Code extension
- browser extension
- demo mode
- code preview
- tags and language labels
Details
- Last Updated
- Nov 6, 2026
- Created
- Dec 7, 2025
- Install Methods
- dockerdocker-composesource
- Requirements
- Docker
- Default Port
- 8080web UI
- Authentication
- local
- API
- REST
- Runtime / Stack
- GoDocker
- Privacy & Independence
- No Cloud RequiredOffline Capable
- Deployment
Deployment: Docker Compose ✓Single Container — minimal hosting footprintsingle container
Run Snipo yourself
Pick how much you want to manage.
netcupBest match
Full control
A small server, then Docker Compose.
About 20 minutes with Docker
Hetzner
Full control
A small server, then Docker Compose.
About 20 minutes with Docker
DigitalOcean
Full control
A small server, then Docker Compose.
About 20 minutes with Docker
1 more way to host
Some links earn us a commission. netcup pays us one and is our preferred VPS host.
Is this your project? Sponsor a listing
Run Snipo with Docker Compose
Compose file from the Snipo project repository.
1 service
≈0.5 GB RAM requested (from Docker memory limits)
docker-compose.prod.yml · @ 6708d7b · scanned Nov 3, 2026
# Production Docker Compose with enhanced security and resource limits
# Usage: docker compose -f docker-compose.yml -f docker-compose.prod.yml up -d
#
# SECURITY BEST PRACTICES FOR PRODUCTION:
# 1. Use SNIPO_MASTER_PASSWORD_HASH instead of SNIPO_MASTER_PASSWORD
# Generate with: docker run --rm ghcr.io/mohamedelashri/snipo:latest hash-password
# 2. Store secrets in Docker secrets or a secrets manager (not in plain .env files)
# 3. Enable network isolation (uncomment networks section below)
# 4. Use a reverse proxy with HTTPS (nginx, traefik, caddy)
# 5. Regularly update the image and rotate passwords
#
# DATABASE MEMORY CONFIGURATION:
# For production environments with limited resources, consider reducing database memory usage:
# Add these environment variables to prevent "out of memory" errors:
# - SNIPO_DB_MMAP_SIZE=67108864 # 64MB instead of 256MB
# - SNIPO_DB_CACHE_SIZE=-1000 # 1MB instead of 2MB
services:
snipo:
# Resource limits
deploy:
resources:
limits:
cpus: '1'
memory: 512M
reservations:
cpus: '0.25'
memory: 128M
restart_policy:
condition: on-failure
delay: 5s
max_attempts: 3
window: 120s
# Additional security hardening
security_opt:
- no-new-privileges:true
- seccomp:unconfined # Adjust based on your security requirements
# Logging configuration for production
logging:
driver: "json-file"
options:
max-size: "10m"
max-file: "3"
compress: "true"
# Health check configuration
healthcheck:
test: ["CMD", "/snipo", "health"]
interval: 30s
timeout: 5s
retries: 3
start_period: 10s
# Network isolation (recommended for production)
# Uncomment to use custom network:
# networks:
# - snipo_network
# Optional: Create isolated network for production
# networks:
# snipo_network:
# driver: bridge
# ipam:
# config:
# - subnet: 172.28.0.0/16
This file may be out of date. Check the Snipo website for current setup steps.
Tags
Track your self-hosted stack
Bookmark software to try, rate tools you've used, and keep your collection in one place.

