Support Hub
Use the built-in assistant, documentation hub, and repository workflows to resolve install, upgrade, AI ops, runtime, routing, and release issues without leaving the platform context.
Installation
Pushpaka supports Docker Compose, Helm, and source-based local development. For the fastest production-style setup, copy .env.example, configure domain and secrets, then run docker compose up -d --build. For Kubernetes, add the Helm repo from pushpaka.vikshro.in/helm and install the pushpaka chart.
AI Operations
Pushpaka v1.0.0 includes AI-assisted operations for deployment log analysis, monitoring workflows, assistant-style troubleshooting, and runbook context. Typical usage is: open a failed deployment, inspect realtime logs, run AI analysis, review remediation hints, then redeploy or roll back.
Deployment Targets
Pushpaka handles Git-based deployments across Docker workflows, Kubernetes-oriented targets, and direct runtime fallback. Teams can run single-binary dev mode, all-in-one production mode, or split API and worker mode with Redis-backed queueing.
Editor And Terminal
Pushpaka includes a built-in Monaco editor and web terminal so operators can inspect, edit, sync, and validate application files without leaving the platform. A common workflow is to open the project editor, sync source, apply a change, validate in terminal, then trigger a redeploy.
Domains And Routing
Pushpaka uses Traefik-based routing with custom domains and automatic TLS provisioning. Add a project domain, point DNS to the Pushpaka entrypoint, wait for provisioning, and validate the certificate and route from the dashboard or docs workflow.
API And Integrations
Pushpaka exposes API endpoints for auth, projects, deployments, logs, AI operations, notifications, webhooks, infrastructure controls, and health checks. It also supports GitHub and GitLab OAuth, incoming webhooks, and Slack, Discord, and SMTP notifications.
Upgrade And Release
Use the Releases page for the latest GitHub release assets and checksums. For packaged deployments, prefer the combined release archives or Docker image. For Helm users, update the repo and upgrade the chart. Always review release notes and verify checksums before rollout.
Troubleshooting
Start with deployment logs, health endpoints, and system status. For failed releases, verify the correct asset name and tag. For routing issues, confirm DNS and TLS state. For build problems, inspect logs, AI analysis output, and configuration such as runtime, build command, and environment variables.