Portainer Templates logo

Portainer Templates

Snibox (stack) Snibox (stack)

Tools

Self-hosted snippet manager.Label-oriented interface with search. Supports various programming languages, markdown, plain text.

Configuration

Type
Compose
Platform
linux
Source
Repo

Template by xneo1·Source

Services

frontend

Configuration

Image
snibox/nginx-puma:1.15.9
Ports
8000:80
Volumes
/var/www/html : static-files

Image details

Pulls: 897k
User: snibox
Created: Feb 07, 2018
Updated: 7 years ago
Status: active

backend

Configuration

Image
snibox/snibox:latest
Command
sh -c "rm -rf tmp/pids && ./bin/rails s -p 3010 -b '0.0.0.0'"
Volumes
/app/public : /portainer/Files/AppData/Config/snibox
Env vars
DB_NAME=${DB_NAME}DB_USER=${DB_USER}DB_PASS=${DB_PASS}DB_HOST=${DB_HOST}DB_PORT=${DB_PORT}FORCE_SSL=${FORCE_SSL}MAILGUN_SMTP_PORT=${MAILGUN_SMTP_PORT}MAILGUN_SMTP_SERVER=${MAILGUN_SMTP_SERVER}MAILGUN_SMTP_LOGIN=${MAILGUN_SMTP_LOGIN}MAILGUN_SMTP_PASSWORD=${MAILGUN_SMTP_PASSWORD}MAILGUN_API_KEY=${MAILGUN_API_KEY}MAILGUN_DOMAIN=${MAILGUN_DOMAIN}MAILGUN_PUBLIC_KEY=${MAILGUN_PUBLIC_KEY}SECRET_KEY_BASE=${SECRET_KEY_BASE}

Image details

Pulls: 986k
User: snibox
Created: Feb 07, 2018
Updated: 7 years ago
Status: active

database

Configuration

Image
postgres:10.7-alpine
Volumes
/var/lib/postgresql/data : /portainer/Files/AppData/Config/snibox/pg-data

Image details

Pulls: 11.2B
User: stackbrew
Created: Jun 05, 2014
Updated: 3 hours ago
Status: active

Standalone Install

Select an install method, to see config/commands for deploying Snibox (stack)

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 Snibox (stack), 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:
  frontend:
    image: snibox/nginx-puma:1.15.9
    ports:
      - "8000:80"
    volumes:
      - static-files:/var/www/html
    depends_on:
      - backend

  backend:
    image: snibox/snibox:latest
    command: sh -c "rm -rf tmp/pids && ./bin/rails s -p 3010 -b '0.0.0.0'"
    environment:
      DB_NAME: "${DB_NAME}"
      DB_USER: "${DB_USER}"
      DB_PASS: "${DB_PASS}"
      DB_HOST: "${DB_HOST}"
      DB_PORT: "${DB_PORT}"
      FORCE_SSL: "${FORCE_SSL}"
      MAILGUN_SMTP_PORT: "${MAILGUN_SMTP_PORT}"
      MAILGUN_SMTP_SERVER: "${MAILGUN_SMTP_SERVER}"
      MAILGUN_SMTP_LOGIN: "${MAILGUN_SMTP_LOGIN}"
      MAILGUN_SMTP_PASSWORD: "${MAILGUN_SMTP_PASSWORD}"
      MAILGUN_API_KEY: "${MAILGUN_API_KEY}"
      MAILGUN_DOMAIN: "${MAILGUN_DOMAIN}"
      MAILGUN_PUBLIC_KEY: "${MAILGUN_PUBLIC_KEY}"
      SECRET_KEY_BASE: "${SECRET_KEY_BASE}"
    volumes:
      - /portainer/Files/AppData/Config/snibox:/app/public
    depends_on:
      - database

  database:
    image: postgres:10.7-alpine
    volumes:
      - /portainer/Files/AppData/Config/snibox/pg-data:/var/lib/postgresql/data

Or deploy it directly from the source:

git clone https://github.com/xneo1/portainer_templates
cd portainer_templates
docker compose -f Template/Stack/snibox.yml up -d

More install options in our documentation.

Container Documentation

database Documentation

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

Serve Snibox (stack) 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 snibox-stack.example.com to http://frontend:80

Add this to your Caddyfile

snibox-stack.example.com {
	reverse_proxy http://frontend:80
}

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.

Port already in use

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

  • Find what's using it: sudo ss -tlnp | grep :8000
  • Stop the other service, or pick a different host port. In 8000:80 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:8000. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, Snibox can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 8000

Permission denied on volumes

If the logs show "permission denied", the app can't write to its data folder on the host.

  • Fix the ownership: sudo chown -R 1000:1000 /portainer/Files/AppData/Config/snibox (and the same for the other mapped folders)

Image won't pull

Test the pull directly on the host: docker pull snibox/nginx-puma:1.15.9

  • "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.

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

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

Snibox (stack) is a Compose stack, a set of containers (3 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 3 containers that run side by side. Here's each one, with the image it runs and anything it waits for first:

  • frontend runs snibox/nginx-puma:1.15.9, starts after backend
  • backend runs snibox/snibox:latest, starts after database
  • database runs postgres:10.7-alpine

Ports

A port is the door the app answers on. A mapping like 8000:80 means it's reachable on port 8000 of your server, where the left number is yours to change and the right one belongs to the app. Once it's running, open http://your-server-ip:8000 in a browser. It opens:

  • 8000:80, likely the web interface

Volumes

A volume is where Snibox (stack) 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:

  • /var/www/html kept in the static-files volume Docker manages
  • /app/public from /portainer/Files/AppData/Config/snibox on the host
  • /var/lib/postgresql/data from /portainer/Files/AppData/Config/snibox/pg-data on the host

Environment variables

Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Snibox (stack) takes 14 of them, all with defaults you can leave alone or tweak:

  • DB_NAME, pulled from your own environment
  • DB_USER, pulled from your own environment
  • DB_PASS, pulled from your own environment
  • DB_HOST, pulled from your own environment
  • DB_PORT, pulled from your own environment
  • FORCE_SSL, pulled from your own environment
  • MAILGUN_SMTP_PORT, pulled from your own environment
  • MAILGUN_SMTP_SERVER, pulled from your own environment
  • MAILGUN_SMTP_LOGIN, pulled from your own environment
  • MAILGUN_SMTP_PASSWORD, pulled from your own environment
  • MAILGUN_API_KEY, pulled from your own environment
  • MAILGUN_DOMAIN, pulled from your own environment
  • MAILGUN_PUBLIC_KEY, pulled from your own environment
  • SECRET_KEY_BASE, pulled from your own environment

Networking

Portainer puts these services on one shared private network, so they can find each other by name (like frontend) 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.

Portainer app templates

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