Portainer Templates logo

Portainer Templates

Opengist Opengist

Container

DevelopmentTools

Pastebin built on Git, like GitHub Gist: every snippet is a repo you can clone, push to and fork, with syntax highlighting, Markdown, embeds, search, and public, unlisted or private gists. Source: https://github.com/thomiceli/opengist

Image details

Architecture: amd64, arm64
Image size: 44 MB
User: thomiceli

Source details

Repo: thomiceli/opengist
Stars: 3k
Forks: 203
Language: Go
License: AGPL-3.0
Latest: v1.15.2 · 1 month ago
Updated: 1 day ago
Website: opengist.io/

Configuration

Type
Container
Platform
linux
Image
ghcr.io/thomiceli/opengist:1
Ports
6157:6157/tcp2222:2222/tcp
Volumes
/opengist
Restart
unless-stopped

Template by NotAFlightRisk

Report issue

Notes

Open http://<your-host>:6157 and register. The first account becomes the admin and sign-ups stay open after it, so once everyone's in, tick Disable signup under Admin --> Configuration (invitations still work). Public gists can be read without logging in unless you tick Require login there too. Every gist is a Git repo: clone and push over http on 6157, or over SSH on 2222 once you've added a key under Settings. Anyone who adds an email gets their avatar from Gravatar, which the same admin page can turn off. Behind an HTTPS proxy, add OG_EXTERNAL_URL (like https://gist.example.com) to the container's environment so the login cookie is Secure and passkeys work. The SQLite database, every gist's repo, the search index and the generated secret key live in the volume. Docs: opengist.io

Standalone Install

Select an install method, to see config/commands for deploying Opengist

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select Opengist, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo

More install options in our documentation, or see thomiceli/opengist for app-specific guidance.

Opengist

Opengist
Opengist is a self-hosted Pastebin powered by Git. All snippets are stored in a Git repository and can be read and/or modified using standard Git commands, or with the web interface. It is similar to GitHub Gist, but open-source and could be self-hosted.
Home Page • Documentation • Discord • Demo
GitHub release (latest SemVer) License Go CI Go Report Card Translate

Features

  • Create public, unlisted or private snippets
  • Init / Clone / Pull / Push snippets via Git over HTTP or SSH
  • Syntax highlighting ; markdown & CSV support
  • Search code in snippets; browse users snippets, likes and forks
  • Add topics to snippets
  • Embed snippets in other websites
  • Revisions history
  • Like / Fork snippets
  • Download raw files or as a ZIP archive
  • OAuth2 login with GitHub, GitLab, Gitea, and OpenID Connect
  • Restrict or unrestrict snippets visibility to anonymous users
  • Docker support / Helm Chart
  • More...

Quick start

With Docker

Docker images are available for each release :
docker pull ghcr.io/thomiceli/opengist:1.15.2

It can be used in a docker-compose.yml file :
  1. Create a docker-compose.yml file with the following content
  2. Run docker compose up -d
  3. Opengist is now running on port 6157, you can browse http://localhost:6157

services:
  opengist:
    image: ghcr.io/thomiceli/opengist:1.15.2
    container_name: opengist
    restart: unless-stopped
    ports:
      - "6157:6157" # HTTP port
      - "2222:2222" # SSH port, can be removed if you don't use SSH
    volumes:
      - "$HOME/.opengist:/opengist"

You can define which user/group should run the container and own the files by setting the UID and GID environment variables :
services:
  opengist:
    # ...
    environment:
      UID: 1001
      GID: 1001

Via binary

Download the archive for your system from the release page here, and extract it.
# example for linux amd64
wget https://github.com/thomiceli/opengist/releases/download/v1.15.2/opengist1.15.2-linux-amd64.tar.gz

tar xzvf opengist1.15.2-linux-amd64.tar.gz
cd opengist
chmod +x opengist
./opengist # with or without `--config config.yml`

Opengist is now running on port 6157, you can browse http://localhost:6157

From source

Requirements: Git (2.28+), Go (1.23+), Node.js (16+), Make (optional, but easier)
git clone https://github.com/thomiceli/opengist
cd opengist
make
./opengist

Opengist is now running on port 6157, you can browse http://localhost:6157
To create and run a development environment, see run-development.md.

Documentation

The documentation is available at https://opengist.io/ or in the /docs directory.

License

Opengist is licensed under the AGPL-3.0 license.

Serve Opengist on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.

Proxying opengist.example.com to http://opengist:6157

Add this to your Caddyfile

opengist.example.com {
	reverse_proxy http://opengist:6157
}

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs opengist
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Port already in use

If deployment fails with "Bind for 0.0.0.0:6157 failed: port is already allocated", something else on your server is using that port.

  • Find what's using it: sudo ss -tlnp | grep :6157
  • Stop the other service, or pick a different host port. In 6157:6157 only the left number is yours to change, the right one belongs to the app.

Running but the page won't load

The container is up but nothing appears in your browser.

  • Use your server's real IP: http://your-server-ip:6157. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, opengist can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 6157

Image won't pull

Test the pull directly on the host: docker pull ghcr.io/thomiceli/opengist:1

  • "manifest unknown" means the tag no longer exists.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • This image supports: amd64, arm64
  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Container keeps restarting

The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.

  • Check the logs right after a restart, the last few lines before it died are the useful ones.
  • Get the exit code with docker inspect opengist --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A single container

Opengist runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.

The app image

An image is the app packed up ready to go, everything Opengist needs bundled into one download. This template pulls ghcr.io/thomiceli/opengist:1, which Docker fetches once (about 44 MB) and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. Opengist's comes from the GitHub Container Registry, published by thomiceli.

Version tags

The bit after the colon in the image name is the version tag. This one pins 1, so every redeploy gives you that exact build until you bump it yourself.

Which machines it runs on

Every image is built for particular CPU types. This one ships for amd64, arm64, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.

Ports

A port is the door the app answers on. A mapping like 6157:6157 means it's reachable on port 6157 of your server, where the left number is yours to change and the right one belongs to the app. It opens:

  • 6157:6157
  • 2222:2222

Volumes

A volume is where Opengist keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /opengist as a volume Docker manages for you

Restart policy

The restart policy here is unless-stopped, so Docker restarts Opengist after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).

Networking

Nothing custom is set, so Opengist sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.

Container name

Once it's deployed, Portainer names the container opengist. That's what you'll spot in the containers list and use in commands like docker logs opengist.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Open source license

Opengist is open source, released under the AGPL-3.0 license. In plain terms the code is out in the open, so you're free to run it and change it to fit what you need.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Opengist up. Add the template list to Portainer once, then deploying Opengist is a click rather than a wall of config.