Deploy taskview

Deploy and Host TaskView on Railway

TaskView is a self-hosted project and task management platform for teams that need clear ownership and flexible workflows. It combines projects, tasks, Kanban boards, dependency graphs, analytics, role-based collaboration, developer integrations, webhooks, and AI/MCP connectivity while keeping application data in a PostgreSQL database you control.

About Hosting TaskView on Railway

Railway runs TaskView as Docker image services for the web UI, API, database migration, and PostgreSQL. The web and API services use Railway domains, while API and migration services connect to PostgreSQL over Railway private networking.

Tech Stack

• Vue web application served by Nginx
• Node.js, Express, TypeScript, and PM2 API server
• PostgreSQL with Drizzle ORM and pg-boss
• Docker images from Docker Hub and GitHub Container Registry
• Railway private networking and persistent volumes

Why Deploy TaskView on Railway

Railway provides one-click provisioning, managed service networking, HTTPS domains, persistent PostgreSQL storage, environment variable management, and straightforward logs and redeploys. This keeps the full TaskView stack deployable without a source build while preserving the upstream container startup behavior.

Common Use Cases

• Team project and task management
• Kanban workflows and dependency planning
• Sprint planning, time tracking, and analytics
• Self-hosted GitHub, GitLab, and Gitea integrations
• Webhook and API automation
• AI-assisted workflows through the TaskView MCP integration

Deployment Notes

• The web service listens on port 80 and is the primary browser entry point.
• The API listens on port 1401 and is exposed through its own Railway domain for browser API calls and integrations.
• PostgreSQL listens privately on port 5432 and persists data at /var/lib/postgresql/data.
• The migration service runs once and exits successfully after applying database migrations; this is expected.
• JWT signing and encryption keys are generated with Railway secret functions.
• Public registration is disabled by default and password login is enabled.
• The upstream migration seeds the initial account with username user and password user1!#Q. Change these credentials immediately after the first login.
• DEFAULT_USERNAME and DEFAULT_PASSWORD are included as visible onboarding variables for the seeded account.
• The web service receives TASKVIEW_API_URL, while the API receives APP_URL, API_PUBLIC_URL, and CORS_ALLOWED_ORIGINS through Railway service references.

Dependencies for TaskView on Railway

TaskView requires the web UI, API, one-time migration runner, and PostgreSQL database. The API and migration services use private references to the PostgreSQL service, and the web UI uses the public API domain.

Deployment Dependencies