Back to articles
AI & Cloud

Self-Host PlanSo on Docker: The Perfect Jira Replacement for Agile Enterprises

A detailed guide on self-hosting PlanSo on Docker to replace Jira, ideal for Agile enterprises needing flexible, self-controlled, and low-cost project management solutions. With...

DPTCloud Engineering4 min read
Self-Host PlanSo on Docker: The Perfect Jira Replacement for Agile Enterprises

Why Choose PlanSo Over Jira?

As Agile enterprises increasingly require flexible, self-controlled, and cost-effective project management tools, Jira, despite its power, presents limitations in pricing, scalability, and data control. PlanSo, a self-hosted project management solution, offers similar features to Jira (task management, Kanban boards, reporting, API integration) but with notable advantages:

  • Data control: Your business data is stored on your own servers, eliminating reliance on SaaS providers.
  • Low cost: No monthly subscription fees—only infrastructure costs (VPS or physical server).
  • High flexibility: Easily integrate with existing systems and customize to meet real-world needs.
  • Scalability: Easily scale as your business grows.

Deploying PlanSo on Docker

Deploying PlanSo on Docker allows you to install, update, and manage versions quickly and consistently. Below is a detailed guide.

Requirements and Prerequisites

  • Server or VPS with at least 4GB RAM and 2 CPU cores (8GB RAM and 4 cores recommended).
  • Operating system: Ubuntu 20.04/22.04 or Debian 11/12.
  • Docker and Docker Compose installed.
  • Domain name (recommended) or static IP for access.
  • Firewall (or network firewall) configured to allow ports 80 (HTTP) and 443 (HTTPS).

Install PlanSo with Docker Compose

After preparing your environment, create a new directory and create a docker-compose.yml file with the following content:

version: '3.8'

services:
  planso:
    image: planso/planso:latest
    container_name: planso
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - ./data:/app/data
    environment:
      - PLANSO_DATABASE_URL=postgresql://user:password@db:5432/planso
      - PLANSO_SECRET_KEY=your-secret-key-here
    depends_on:
      - db
    restart: unless-stopped

  db:
    image: postgres:14
    container_name: planso_db
    environment:
      - POSTGRES_DB=planso
      - POSTGRES_USER=user
      - POSTGRES_PASSWORD=password
    volumes:
      - ./db_data:/var/lib/postgresql/data
    restart: unless-stopped

Run the following command to start the services:

docker-compose up -d

PlanSo will start on ports 80 and 443. After a few minutes, access your server's IP or domain to complete the initial setup.

Restore Data from Jira (if needed)

PlanSo supports exporting data from Jira via API or CSV format. You can:

  • Export tasks, projects, and users from Jira into CSV files.
  • Use a data conversion tool (if available) or manually import into PlanSo.
  • Integrate with Jira’s API for real-time data synchronization (requires additional development).

Management and Integration

Version Management and Updates

To update PlanSo to a newer version, run:

docker-compose pull planso
docker-compose up -d

PlanSo will automatically update the container without losing data.

Integration with Existing Systems

PlanSo provides a full REST API and supports integration with tools such as:

  • CI/CD (Jenkins, GitLab CI)
  • Chat (Slack, Microsoft Teams)
  • Data analytics (Power BI, Metabase)

To integrate, you need to:

  1. Create an API key in PlanSo.
  2. Set up webhooks or call the API as required.
  3. Test with third-party tools.

Verification and Troubleshooting

Troubleshooting

  • Cannot access the website: Check firewall rules, ports, and Docker logs using docker-compose logs planso.
  • Database connection failed: Verify the PLANSO_DATABASE_URL environment variable and the status of the db container.
  • Cannot log in: Ensure data has been created in the ./data directory or reset it by deleting this folder (only for testing environments).

Performance Monitoring

To monitor performance, you can:

  • Monitor server resources (CPU, RAM) using htop or docker stats.
  • Analyze logs using GoAccess if PlanSo runs behind Nginx.
  • Set up alerts using dedicated servers if high load is expected.

References

Assumptions: The user has basic knowledge of Docker, Linux, and system administration. This guide does not include SSL or DNS configuration. For more information, refer to the guide on configuring proxies and domains.

DPTCloud Tier III Infrastructure

High-RAM Cloud VPS Plans Optimized for AI, Databases & Cache

Enterprise RAID 10 NVMe SSDs, CMC & FPT District 9 uplinks with Anycast Anti-DDoS and 99.99% SLA.

View 22 VPS Plans
ECO · vn-02Recommended

VPS-4E

297.000 ₫ / mo

10% VAT included

  • CPU: 4 vCPU
  • RAM: 8 GB
  • SSD: 50 GB NVMe
ECO · vn-02

VPS-5E

614.900 ₫ / mo

10% VAT included

  • CPU: 8 vCPU
  • RAM: 16 GB
  • SSD: 100 GB NVMe
ADVANCED · vn-03Recommended

VPS-4T

548.900 ₫ / mo

10% VAT included

  • CPU: 4 vCPU
  • RAM: 8 GB
  • SSD: 50 GB NVMe

Related Articles

View all
ZaloZalo SupportDiscord0384 753 478