Life Console
Stack
Keyboard-first planner that shows what to do right now: time-block your week, count down deadlines and link tasks to goals.
Configuration
TypeComposelinuxPOSTGRES_PASSWORD=''LC_PORT=8080APP_URL=''unless-stoppedNotes
openssl rand -hex 32 makes a good one); the stack won't start without it. Then open http://<your-host>:<Web UI port> (the port you chose above, 8080 by default) and create your account: it becomes the admin. Sign-ups start closed, so nobody else can create an account until you open them in Settings → Sign-ups. Update with Stacks → life-console → Pull and redeploy. Docs: life-console.dev/docs/self-hostingServices
app
Configuration
Imageghcr.io/tj-coding/life-console:latest${LC_PORT:-8080}:8080/backups : backupsDATABASE_URL=postgres://lifeconsole:${POSTGRES_PASSWORD:?set a database password}@db:5432/lifeconsoleAPP_URL=${APP_URL:-}SIGNUPS=${SIGNUPS:-closed}AUTH_PASSWORD=onBACKUP_DIR=/backupsunless-stoppedImage details
db
Configuration
Imagepostgres:17-alpine/var/lib/postgresql/data : dbPOSTGRES_USER=lifeconsolePOSTGRES_PASSWORD=${POSTGRES_PASSWORD:?set a database password}POSTGRES_DB=lifeconsoleunless-stoppedImage details
Standalone Install
Select an install method, to see config/commands for deploying Life Console
Install on Portainer
Import all app templates into your Portainer instance, for easy 1-click deploys
- Ensure both Docker and Portainer are installed, and up-to-date
- Log into your Portainer web UI
- Under Settings → App Templates, paste the below URL
- Head to Home → App Templates, and the list of apps will show up
- Select Life Console, fill in any config options, and hit Deploy
Template Import URL
https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me
Original stackfile
The compose file this template deploys, straight from its repo:
# Life Console for Portainer (stack template: packaging/portainer/portainer-template.json).
# Portainer fills the ${VARIABLES} from the template's form. To update: Stacks → life-console → Pull and redeploy.
services:
app:
image: ghcr.io/tj-coding/life-console:latest
restart: unless-stopped
depends_on:
db: { condition: service_healthy }
environment:
DATABASE_URL: postgres://lifeconsole:${POSTGRES_PASSWORD:?set a database password}@db:5432/lifeconsole
APP_URL: ${APP_URL:-}
# closed: only the first account (the admin) can sign up; admins open sign-ups in Settings → Sign-ups
SIGNUPS: ${SIGNUPS:-closed}
AUTH_PASSWORD: "on"
BACKUP_DIR: /backups
ports:
- "${LC_PORT:-8080}:8080"
volumes:
- backups:/backups
db:
image: postgres:17-alpine
restart: unless-stopped
environment:
POSTGRES_USER: lifeconsole
POSTGRES_PASSWORD: ${POSTGRES_PASSWORD:?set a database password}
POSTGRES_DB: lifeconsole
healthcheck:
test: ["CMD-SHELL", "pg_isready -U lifeconsole -d lifeconsole"]
interval: 5s
timeout: 3s
retries: 20
volumes:
- db:/var/lib/postgresql/data
volumes:
db:
backups:
Or deploy it directly from the source:
git clone https://github.com/TJ-coding/life-console
cd life-console
docker compose -f packaging/portainer/docker-compose.yml up -dMore install options in our documentation.
Container Documentation
db 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:
137means killed, usually out of memory.126or127means the command inside the image is broken.
Image won't pull
Test the pull directly on the host: docker pull ghcr.io/tj-coding/life-console: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 loginto 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
noso 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.
- Bug within the app: Open an issue within life-console's repo
- Template not working: Open an issue on TJ-coding/life-console
- This website not working: Open an issue on lissy93/portainer-templates
A Compose stack
Life Console 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:
apprunsghcr.io/tj-coding/life-console:latest, starts after dbdbrunspostgres:17-alpine
Volumes
A volume is where Life Console 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:
/backupskept in thebackupsvolume Docker manages/var/lib/postgresql/datakept in thedbvolume Docker manages
Environment variables
Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Life Console takes 8 of them, and one needs a value before it'll start properly:
DATABASE_URL, defaults topostgres://lifeconsole:@db:5432/lifeconsoleAPP_URL, pulled from your own environmentSIGNUPS, defaults toclosedAUTH_PASSWORD, defaults toonBACKUP_DIR, defaults to/backupsPOSTGRES_USER, defaults tolifeconsolePOSTGRES_PASSWORD, needs a valuePOSTGRES_DB, defaults tolifeconsole
Restart policy
The restart policy here is unless-stopped, so Docker restarts Life Console 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 app) 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 Life Console up. Add the template list to Portainer once, then deploying Life Console is a click rather than a wall of config.