Portainer Templates logo

Portainer Templates

Zipline Zipline

Stack

File Sharing

File sharing and screenshot host that works with ShareX, Flameshot and the like, with a link shortener, text pastes, folders, and files that can expire, need a password or delete themselves after so many views. Source: https://github.com/diced/zipline

Source details

Repo: diced/zipline
Stars: 3k
Forks: 256
Language: TypeScript
License: MIT
Latest: v4.8.0 · 20 days ago
Updated: 4 hours ago
Website: zipline.diced.sh/

Configuration

Type
Compose
Platform
linux
Env vars
ZIPLINE_SECRET=''ZIPLINE_DB_PASSWORD=''ZIPLINE_PORT=3200
Restart
unless-stopped
Source
Repo

Template by NotAFlightRisk·Source

Report issue

Notes

Set both secrets before you deploy (openssl rand -hex 32 makes good ones), since the stack won't start without them, and keep them the same when you redeploy. Then open http://<your-host>:3200 (or whichever port you picked) and create the first account, which becomes the super admin. There are no open sign-ups, so you add everyone else under Users. Settings, under your name in the top corner, makes ready-to-use ShareX and Flameshot configs. Links use whatever address you opened it on, and the rest of the settings (domains, HTTPS links, sign-ups, the 100 MB file limit) live in the dashboard under Server Settings. It checks GitHub for new versions, which you can switch off there under Features. Files and thumbnails live in the zipline-uploads volume, everything else in postgres-data. Docs: zipline.diced.sh

Services

zipline

Configuration

Image
ghcr.io/diced/zipline:latest
Ports
${ZIPLINE_PORT:-3200}:3000
Volumes
/zipline/uploads : zipline-uploads
Env vars
CORE_SECRET=${ZIPLINE_SECRET:?Set a secret of at least 32 characters}DATABASE_URL=postgres://zipline:${ZIPLINE_DB_PASSWORD:?Set a database password}@postgres:5432/zipline
Restart
unless-stopped

Image details

User: diced

postgres

Configuration

Image
postgres:17-alpine
Volumes
/var/lib/postgresql/data : postgres-data
Env vars
POSTGRES_DB=ziplinePOSTGRES_USER=ziplinePOSTGRES_PASSWORD=${ZIPLINE_DB_PASSWORD:?Set a database password}
Restart
unless-stopped

Image details

Pulls: 11.9B
User: stackbrew
Created: Jun 05, 2014
Updated: 22 hours ago
Status: active

Standalone Install

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

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 Zipline, fill in any config options, and hit Deploy

Template Import URL

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

The compose file this template deploys, straight from its repo:

services:
  zipline:
    image: ghcr.io/diced/zipline:latest
    restart: unless-stopped
    ports:
      - "${ZIPLINE_PORT:-3200}:3000"
    environment:
      CORE_SECRET: ${ZIPLINE_SECRET:?Set a secret of at least 32 characters}
      DATABASE_URL: postgres://zipline:${ZIPLINE_DB_PASSWORD:?Set a database password}@postgres:5432/zipline
    volumes:
      - zipline-uploads:/zipline/uploads
    depends_on:
      postgres:
        condition: service_healthy

  postgres:
    image: postgres:17-alpine
    restart: unless-stopped
    environment:
      POSTGRES_DB: zipline
      POSTGRES_USER: zipline
      POSTGRES_PASSWORD: ${ZIPLINE_DB_PASSWORD:?Set a database password}
    volumes:
      - postgres-data:/var/lib/postgresql/data
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U zipline -d zipline"]
      interval: 10s
      timeout: 5s
      retries: 5

volumes:
  zipline-uploads:
  postgres-data:

Or deploy it directly from the source:

git clone https://github.com/NotAFlightRisk/portainer-templates-extras
cd portainer-templates-extras
docker compose -f apps/zipline/compose.yml up -d

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

Container Documentation

postgres Documentation

The PostgreSQL object-relational database system provides reliability and data integrity.

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 <container>
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Image won't pull

Test the pull directly on the host: docker pull ghcr.io/diced/zipline:latest

  • "manifest unknown" means the tag no longer exists. This template uses latest, so try pinning a specific version instead.
  • "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.

  • 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 <container> --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Stack won't deploy

Compose stacks fail fast on small mistakes, and Portainer shows the reason just above the editor.

  • YAML only accepts spaces for indentation, a single tab breaks the whole file.

Raise an issue

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

A Compose stack

Zipline is a Compose stack, a set of containers (2 of them) defined in one file and brought up together by Portainer, then started and stopped as a single app.

The services

This stack is built from 2 containers that run side by side. Here's each one, with the image it runs and anything it waits for first:

  • zipline runs ghcr.io/diced/zipline:latest, starts after postgres
  • postgres runs postgres:17-alpine

Volumes

A volume is where Zipline 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:

  • /zipline/uploads kept in the zipline-uploads volume Docker manages
  • /var/lib/postgresql/data kept in the postgres-data volume Docker manages

Environment variables

Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Zipline takes 5 of them, and 2 need a value before it'll start properly:

  • CORE_SECRET, needs a value
  • DATABASE_URL, defaults to postgres://zipline:@postgres:5432/zipline
  • POSTGRES_DB, defaults to zipline
  • POSTGRES_USER, defaults to zipline
  • POSTGRES_PASSWORD, needs a value

Restart policy

The restart policy here is unless-stopped, so Docker restarts Zipline 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

Portainer puts these services on one shared private network, so they can find each other by name (like zipline) while only the ports above are open to you.

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

Zipline is open source, released under the MIT 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 Zipline up. Add the template list to Portainer once, then deploying Zipline is a click rather than a wall of config.