Portainer Templates logo

Portainer Templates

PriceGhost PriceGhost

Stack

Shopping

A self-hosted price tracking application that monitors product prices from any website.Get notified when prices drop, hit your target price, or items come back in stock.

Configuration

Type
Compose
Platform
linux
Source

Template by xneo1·Source

Services

priceghost-postgres

Configuration

Image
postgres:16-alpine
Ports
5432:5432
Volumes
/var/lib/postgresql/data : priceghost-postgres_data/docker-entrypoint-initdb.d/init.sql : ./database/init.sql
Env vars
POSTGRES_USER=postgresPOSTGRES_PASSWORD=postgresPOSTGRES_DB=priceghost
Restart
unless-stopped

Image details

Pulls: 11.2B
User: stackbrew
Created: Jun 05, 2014
Updated: 39 minutes ago
Status: active

priceghost-backend

Configuration

Image
ghcr.io/clucraft/priceghost-backend:latest
Ports
3001:3001
Env vars
DATABASE_URL=postgresql://postgres:postgres@postgres:5432/priceghostJWT_SECRET=${JWT_SECRET:-change-this-in-production-use-strong-secret}PORT=3001NODE_ENV=production
Restart
unless-stopped

Image details

User: clucraft

priceghost-frontend

Configuration

Image
ghcr.io/clucraft/priceghost-frontend:latest
Ports
80:80
Restart
unless-stopped

Image details

User: clucraft

Standalone Install

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

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 PriceGhost, 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:

version: '3.8'

services:
  # PostgreSQL Database
  priceghost-postgres:
    image: postgres:16-alpine
    container_name: priceghost-db
    environment:
      POSTGRES_USER: postgres
      POSTGRES_PASSWORD: postgres
      POSTGRES_DB: priceghost
    volumes:
      - priceghost-postgres_data:/var/lib/postgresql/data
      - ./database/init.sql:/docker-entrypoint-initdb.d/init.sql:ro
    ports:
      - "5432:5432"
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U postgres"]
      interval: 10s
      timeout: 5s
      retries: 5
    restart: unless-stopped

  # Backend API
  priceghost-backend:
    image: ghcr.io/clucraft/priceghost-backend:latest
    container_name: priceghost-backend
    environment:
      DATABASE_URL: postgresql://postgres:postgres@postgres:5432/priceghost
      JWT_SECRET: ${JWT_SECRET:-change-this-in-production-use-strong-secret}
      PORT: 3001
      NODE_ENV: production
    ports:
      - "3001:3001"
    depends_on:
      postgres:
        condition: service_healthy
    restart: unless-stopped

  # Frontend
  priceghost-frontend:
    image: ghcr.io/clucraft/priceghost-frontend:latest
    container_name: priceghost-frontend
    ports:
      - "80:80"
    depends_on:
      - backend
    restart: unless-stopped

volumes:
  priceghost-postgres_data:

Or deploy it directly from the source:

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

More install options in our documentation.

Container Documentation

priceghost-postgres Documentation

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

Serve PriceGhost 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 priceghost.example.com to http://priceghost-frontend:80

Add this to your Caddyfile

priceghost.example.com {
	reverse_proxy http://priceghost-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:5432 failed: port is already allocated", something else on your server is using that port.

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

Image won't pull

Test the pull directly on the host: docker pull postgres:16-alpine

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

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.
  • Relative volume paths like ./database/init.sql often fail in Portainer because there's no working directory. Swap them for absolute paths.

Raise an issue

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

A Compose stack

PriceGhost 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:

  • priceghost-postgres runs postgres:16-alpine
  • priceghost-backend runs ghcr.io/clucraft/priceghost-backend:latest
  • priceghost-frontend runs ghcr.io/clucraft/priceghost-frontend:latest

Ports

A port is the door the app answers on. A mapping like 5432:5432 means it's reachable on port 5432 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:80 in a browser. It opens:

  • 5432:5432
  • 3001:3001
  • 80:80, likely the web interface

Volumes

A volume is where PriceGhost 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/lib/postgresql/data kept in the priceghost-postgres_data volume Docker manages
  • /docker-entrypoint-initdb.d/init.sql from ./database/init.sql on the host

Environment variables

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

  • POSTGRES_USER, defaults to postgres
  • POSTGRES_PASSWORD, defaults to postgres
  • POSTGRES_DB, defaults to priceghost
  • DATABASE_URL, defaults to postgresql://postgres:postgres@postgres:5432/priceghost
  • JWT_SECRET, defaults to change-this-in-production-use-strong-secret
  • PORT, defaults to 3001
  • NODE_ENV, defaults to production

Restart policy

The restart policy here is unless-stopped, so Docker restarts PriceGhost 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 priceghost-postgres) 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 PriceGhost up. Add the template list to Portainer once, then deploying PriceGhost is a click rather than a wall of config.