Portainer Templates logo

Portainer Templates

LynxPrompt LynxPrompt

Stack

DevelopmentProductivity

Self-hostable AI config management platform for AGENTS.md, CLAUDE.md, Cursor rules, and 30+ AI assistant formats. Source: https://github.com/GeiserX/LynxPrompt

Source details

Stars: 60
Forks: 6
Language: TypeScript
License: AGPL-3.0
Updated: 5 days ago
Website: lynxprompt.com/

Configuration

Type
Compose
Platform
linux
Env vars
NEXTAUTH_SECRET=''DB_PASSWORD=''APP_URL=''SMTP_HOST=''SMTP_FROM=''SMTP_PORT=587SMTP_USER=SMTP_PASSWORD=SUPERADMIN_EMAIL=
Restart
unless-stopped
Source

Notes

LynxPrompt listens on port 3000 and keeps its database in the pgdata volume and uploaded images in the uploads volume. Sign-in is a link sent by mail, so fill in the SMTP fields, and set APP_URL to the address you open it on. Generate the secrets with openssl rand -hex 32 and openssl rand -hex 24. All options: https://github.com/GeiserX/LynxPrompt/blob/main/env.example

Services

postgres

Configuration

Image
postgres:18-alpine
Volumes
/var/lib/postgresql : pgdata
Env vars
POSTGRES_DB=lynxpromptPOSTGRES_USER=lynxpromptPOSTGRES_PASSWORD=${DB_PASSWORD:?DB_PASSWORD must be set}
Restart
unless-stopped

Image details

Pulls: 12.6B
User: stackbrew
Created: Jun 05, 2014
Updated: 2 hours ago
Status: active

lynxprompt

Configuration

Image
drumsergio/lynxprompt:2.1.40
Ports
3000:3000
Volumes
/data/uploads : uploads
Env vars
DB_APP_HOST=postgresDB_APP_USER=lynxpromptDB_APP_PASSWORD=${DB_PASSWORD}DB_APP_NAME=lynxpromptDB_USERS_HOST=postgresDB_USERS_USER=lynxpromptDB_USERS_PASSWORD=${DB_PASSWORD}DB_USERS_NAME=lynxprompt_usersDB_BLOG_HOST=postgresDB_BLOG_USER=lynxpromptDB_BLOG_PASSWORD=${DB_PASSWORD}DB_BLOG_NAME=lynxprompt_blogDB_SUPPORT_HOST=postgresDB_SUPPORT_USER=lynxpromptDB_SUPPORT_PASSWORD=${DB_PASSWORD}DB_SUPPORT_NAME=lynxprompt_supportNEXTAUTH_SECRET=${NEXTAUTH_SECRET:?NEXTAUTH_SECRET must be set}NEXTAUTH_URL=${APP_URL:?APP_URL must be set}APP_URL=${APP_URL:?APP_URL must be set}SUPERADMIN_EMAIL=${SUPERADMIN_EMAIL:-}SMTP_HOST=${SMTP_HOST:?SMTP_HOST must be set}SMTP_PORT=${SMTP_PORT:-587}SMTP_USER=${SMTP_USER:-}SMTP_PASSWORD=${SMTP_PASSWORD:-}SMTP_FROM=${SMTP_FROM:?SMTP_FROM must be set}
Restart
unless-stopped

Image details

Pulls: 24.9k
User: drumsergio
Created: Feb 08, 2026
Updated: 23 days ago
Status: active

Standalone Install

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

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 LynxPrompt, 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:
  postgres:
    image: postgres:18-alpine
    restart: unless-stopped
    volumes:
      # Postgres 18 refuses a mount at /var/lib/postgresql/data.
      - pgdata:/var/lib/postgresql
    environment:
      POSTGRES_DB: lynxprompt
      POSTGRES_USER: lynxprompt
      POSTGRES_PASSWORD: ${DB_PASSWORD:?DB_PASSWORD must be set}
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U lynxprompt -d lynxprompt"]
      interval: 5s
      timeout: 5s
      retries: 5

  lynxprompt:
    image: drumsergio/lynxprompt:2.1.40
    platform: linux/amd64
    restart: unless-stopped
    ports:
      - "3000:3000"
    volumes:
      - uploads:/data/uploads
    depends_on:
      postgres:
        condition: service_healthy
    environment:
      # One database per Prisma schema; the app creates the other three on first start.
      DB_APP_HOST: postgres
      DB_APP_USER: lynxprompt
      DB_APP_PASSWORD: ${DB_PASSWORD}
      DB_APP_NAME: lynxprompt
      DB_USERS_HOST: postgres
      DB_USERS_USER: lynxprompt
      DB_USERS_PASSWORD: ${DB_PASSWORD}
      DB_USERS_NAME: lynxprompt_users
      DB_BLOG_HOST: postgres
      DB_BLOG_USER: lynxprompt
      DB_BLOG_PASSWORD: ${DB_PASSWORD}
      DB_BLOG_NAME: lynxprompt_blog
      DB_SUPPORT_HOST: postgres
      DB_SUPPORT_USER: lynxprompt
      DB_SUPPORT_PASSWORD: ${DB_PASSWORD}
      DB_SUPPORT_NAME: lynxprompt_support
      NEXTAUTH_SECRET: ${NEXTAUTH_SECRET:?NEXTAUTH_SECRET must be set}
      NEXTAUTH_URL: ${APP_URL:?APP_URL must be set}
      APP_URL: ${APP_URL:?APP_URL must be set}
      SUPERADMIN_EMAIL: ${SUPERADMIN_EMAIL:-}
      # Sign-in is a link sent by mail, so SMTP is needed to log in.
      SMTP_HOST: ${SMTP_HOST:?SMTP_HOST must be set}
      SMTP_PORT: ${SMTP_PORT:-587}
      SMTP_USER: ${SMTP_USER:-}
      SMTP_PASSWORD: ${SMTP_PASSWORD:-}
      SMTP_FROM: ${SMTP_FROM:?SMTP_FROM must be set}

volumes:
  pgdata:
  uploads:

Or deploy it directly from the source:

git clone https://github.com/lissy93/portainer-templates
cd portainer-templates
docker compose -f sources/stacks/lynxprompt.yml up -d

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

Container Documentation

postgres Documentation

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

lynxprompt Documentation

Serve LynxPrompt 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 lynxprompt.example.com to http://lynxprompt:3000

Add this to your Caddyfile

lynxprompt.example.com {
	reverse_proxy http://lynxprompt:3000
}

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:3000 failed: port is already allocated", something else on your server is using that port.

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

Image won't pull

Test the pull directly on the host: docker pull postgres:18-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.

Raise an issue

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

A Compose stack

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

  • postgres runs postgres:18-alpine
  • lynxprompt runs drumsergio/lynxprompt:2.1.40, starts after postgres

Ports

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

  • 3000:3000, likely the web interface

Volumes

A volume is where LynxPrompt 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 kept in the pgdata volume Docker manages
  • /data/uploads kept in the uploads volume Docker manages

Environment variables

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

  • POSTGRES_DB, defaults to lynxprompt
  • POSTGRES_USER, defaults to lynxprompt
  • POSTGRES_PASSWORD, needs a value
  • DB_APP_HOST, defaults to postgres
  • DB_APP_USER, defaults to lynxprompt
  • DB_APP_PASSWORD, pulled from your own environment
  • DB_APP_NAME, defaults to lynxprompt
  • DB_USERS_HOST, defaults to postgres
  • DB_USERS_USER, defaults to lynxprompt
  • DB_USERS_PASSWORD, pulled from your own environment
  • DB_USERS_NAME, defaults to lynxprompt_users
  • DB_BLOG_HOST, defaults to postgres
  • DB_BLOG_USER, defaults to lynxprompt
  • DB_BLOG_PASSWORD, pulled from your own environment
  • DB_BLOG_NAME, defaults to lynxprompt_blog
  • DB_SUPPORT_HOST, defaults to postgres
  • DB_SUPPORT_USER, defaults to lynxprompt
  • DB_SUPPORT_PASSWORD, pulled from your own environment
  • DB_SUPPORT_NAME, defaults to lynxprompt_support
  • NEXTAUTH_SECRET, needs a value
  • NEXTAUTH_URL, needs a value
  • APP_URL, needs a value
  • SUPERADMIN_EMAIL, pulled from your own environment
  • SMTP_HOST, needs a value
  • SMTP_PORT, defaults to 587
  • SMTP_USER, pulled from your own environment
  • SMTP_PASSWORD, pulled from your own environment
  • SMTP_FROM, needs a value

Restart policy

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

Open source license

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