01One-command Docker
Fresh Linux VM or homelab box
Command
shellcurl -fsSL https://raw.githubusercontent.com/neuraparse/taskNebula/main/scripts/quickstart.sh | bash000TASKNEBULA OPERATIONS
Self-hosting that stays boring on purpose.
TaskNebula's repo is Docker-first: published image, PostgreSQL 16 with pgvector, Redis 7, optional LiveKit voice rooms, optional cron sidecar, health checks, and explicit update paths.
Docker-firstPinned image v0.7.11GET /api/health
Docker ComposePostgreSQL 16 + pgvectorRedis 7Optional LiveKitCron sidecar
FIG 01 · Dashboard — Standup, catch-up, analytics, deadlines, pinned work, and recent activity.
v0.7.11
Latest release
30
Locales
36
GitHub stars · 12 Jul 2026
MIT
License
001Install matrix
Pick the path that matches the machine.
The README separates a fresh Linux VM, local Docker Desktop demo, pinned production release, and source build. The public page should do the same instead of pretending one command fits every operator.
02Docker Desktop
Local Mac, Windows, Linux, or WSL demo
Command
shellcurl -fsSLo compose.yml https://raw.githubusercontent.com/neuraparse/taskNebula/main/docker-compose.desktop.yml && docker compose up -d03Pinned production
Repeatable self-hosted release
Command
shellTASKNEBULA_IMAGE=neuraparse/tasknebula:0.7.11 docker compose up -d04Source build
Local patching or contribution
Command
shellgit clone https://github.com/neuraparse/taskNebula.git && cd taskNebula && docker compose up -d --build002Topology
One web container, persistent stores, explicit optional services.
The production Compose file keeps core services always-on and gates automation behind profiles. That reduces surprise-on services for first-time self-hosters.
01Published image first
The default production path pulls neuraparse/tasknebula, while source builds stay available for teams patching the repo.
latest0.7.11source build
02Localhost-bound services
The production Compose file binds database, Redis, and web ports to 127.0.0.1 by default so a reverse proxy can own the public edge.
127.0.0.1TLS proxyhealth checks
03No Docker socket in web
Self-update is deliberately a signed handoff to an operator-managed updater. The app container does not need Docker socket access.
signed requestmanual fallbackoperator control
Compose dependency graphOperating flow
- 01
PostgreSQL 16 + pgvector
persistent volume
- 02
Redis 7 with password
cache + pub/sub
- 03
Optional LiveKit
voice rooms
- 04
TaskNebula web
GET /api/health
- 05
Optional cron sidecar
standup/janitor/version-check
003Production checklist
The operator contract is explicit.
TaskNebula's self-host story is strongest when it says exactly what should be pinned, generated, backed up, exposed, and checked.
01Image
Pin TASKNEBULA_IMAGE=neuraparse/tasknebula:0.7.11 outside quick demos.
02Secrets
Generate AUTH_SECRET, REDIS_PASSWORD, and LIVEKIT_API_SECRET per install.
03Network
Keep Compose ports bound to 127.0.0.1 and expose through TLS reverse proxy.
04Persistence
Back up postgres_data, redis_data, and uploads_data.
05Updates
Pull image, restart, then verify GET /api/health.
06Automation
Enable cron only with docker compose --profile cron up -d cron.
07AI
Prefer Admin -> Agent control and workspace settings over long-lived env keys.
004Update flow
Updates are visible, but not magical.
The app can detect Docker Hub image pushes, notify super-admins, and send an opt-in signed handoff to an external updater. Manual Docker commands remain first-class.
Pinned update command
shelldocker compose pull web && docker compose up -d
curl -fsS http://localhost:3000/api/healthSource record
Verified from docker-compose.yml, docker-compose.desktop.yml, and the README on June 23, 2026. Deploy ports stay localhost-bound by default and the web container does not receive Docker socket access.
Run it yourself
Pull the image, keep the data, wire your own AI keys.
TaskNebula is positioned as the self-hostable project-management control plane for teams that want inspectable operations, not another black-box SaaS.