Long-term fix for mobile task index - task numbers now in frontmatter. Numbers added from BACKLOG.md cross-reference: #2 rank-system-deployment #3 fire-frost-holdings-restructuring #14 vaultwarden-ssh-setup #22 netdata-deployment #23 department-structure #26 modpack-version-checker #32 terraria-branding-training-arc #35 pokerole-wikijs-deployment #36 notebooklm-integration #40 world-backup-automation #44 nc1-node-usage-stats #45 steam-and-state-server #48 n8n-rebuild #51 ignis-protocol #55 discord-invite-setup #65 claude-infrastructure-access #67 nc1-security-monitoring #82 plane-decommissioning #87 arbiter-2-1-cancellation-flow #89 staff-portal-consolidation #90 decap-tasks-collection #91 server-matrix-node-fix #92 desktop-mcp #93 trinity-codex #94 global-restart-scheduler #98 discord-channel-automation #99 claude-projects-architecture Chronicler #69
199 lines
4.7 KiB
Markdown
199 lines
4.7 KiB
Markdown
---
|
|
task_number: 82
|
|
status: open
|
|
priority: P3
|
|
owner: Michael
|
|
created: 2026-03-26
|
|
---
|
|
task_number: 82
|
|
|
|
# Task #82: Decommission Plane Project Management
|
|
|
|
**Created:** March 26, 2026
|
|
**Status:** 🟡 PENDING
|
|
**Priority:** Medium
|
|
**Time Estimate:** 30 minutes
|
|
**Assigned To:** Next Chronicler
|
|
|
|
---
|
|
task_number: 82
|
|
|
|
## Overview
|
|
|
|
Remove Plane project management system from TX1 Dallas server. Plane was successfully deployed but did not fit Firefrost's workflow. Team switched to Gitea's built-in Kanban project boards instead.
|
|
|
|
**Decision Context:**
|
|
- Plane worked technically (5 projects created, members invited, labels configured)
|
|
- Gitea↔Plane sync via n8n had issues (webhook loop crash)
|
|
- Gitea Kanban projects proved to be better fit for team workflow
|
|
- Plane adds unnecessary complexity and resource usage
|
|
|
|
---
|
|
task_number: 82
|
|
|
|
## What Was Plane?
|
|
|
|
**Deployment Details:**
|
|
- **Location:** TX1 Dallas (38.68.14.26)
|
|
- **URL:** tasks.firefrostgaming.com
|
|
- **Port:** 8090 (proxied via Nginx)
|
|
- **Version:** Plane v2.4.2 (self-hosted)
|
|
- **Installation Path:** `/opt/plane/`
|
|
|
|
**What Was Created:**
|
|
- 5 projects: Infrastructure, Community, Content, Builds, Operations
|
|
- 14 labels in Fire/Frost brand colors
|
|
- Meg and Holly invited as members
|
|
- Workspace: `firefrost-tasks`
|
|
|
|
**Integration Attempts:**
|
|
- n8n workflow: Gitea issue → Plane task (working)
|
|
- n8n workflow: Plane → Gitea (webhook loop, deactivated)
|
|
|
|
---
|
|
task_number: 82
|
|
|
|
## Decommissioning Steps
|
|
|
|
### Step 1: Stop Plane Services
|
|
|
|
SSH to TX1:
|
|
```bash
|
|
ssh root@38.68.14.26
|
|
cd /opt/plane
|
|
docker-compose ps
|
|
docker-compose down
|
|
```
|
|
|
|
### Step 2: Remove Nginx Configuration
|
|
|
|
```bash
|
|
rm /etc/nginx/sites-enabled/plane
|
|
rm /etc/nginx/sites-available/plane
|
|
nginx -t && systemctl reload nginx
|
|
```
|
|
|
|
### Step 3: Backup Data (Optional)
|
|
|
|
If you want to preserve Plane data before deletion:
|
|
```bash
|
|
cd /opt/plane
|
|
tar -czf /root/plane-backup-$(date +%Y%m%d).tar.gz volumes/
|
|
```
|
|
|
|
### Step 4: Remove Plane Installation
|
|
|
|
**CAUTION:** This permanently deletes all Plane data.
|
|
|
|
```bash
|
|
cd /opt/plane
|
|
docker-compose down -v # Removes containers AND volumes
|
|
cd /opt
|
|
rm -rf plane/
|
|
```
|
|
|
|
### Step 5: Remove DNS Record
|
|
|
|
**Option A:** Remove `tasks.firefrostgaming.com` DNS A record entirely
|
|
|
|
**Option B:** Repurpose subdomain for something else (decide before removing)
|
|
|
|
### Step 6: Remove n8n Workflows
|
|
|
|
Check n8n for Plane-related workflows:
|
|
- "Gitea Issue → Plane Task" (was working, now obsolete)
|
|
- "Plane Task → Gitea Issue" (was deactivated due to webhook loop)
|
|
|
|
Delete or archive these workflows.
|
|
|
|
---
|
|
task_number: 82
|
|
|
|
## Documentation Updates
|
|
|
|
Update these files after decommissioning:
|
|
|
|
1. **docs/core/infrastructure-manifest.md**
|
|
- Remove Plane from TX1 service list
|
|
- Update port 8090 status to "available"
|
|
|
|
2. **docs/core/tasks.md**
|
|
- Mark this task as COMPLETE
|
|
- Remove any Plane-related tasks
|
|
|
|
3. **SESSION-HANDOFF-NEXT.md**
|
|
- Remove Plane references from pending items
|
|
|
|
4. **docs/tasks/gitea-plane-integration/**
|
|
- Mark directory as ABANDONED
|
|
- Add README explaining why integration was abandoned
|
|
|
|
---
|
|
task_number: 82
|
|
|
|
## Verification
|
|
|
|
After decommissioning, verify:
|
|
|
|
- [ ] `docker ps` on TX1 shows no Plane containers
|
|
- [ ] `https://tasks.firefrostgaming.com` returns connection error (or redirects if repurposed)
|
|
- [ ] Port 8090 freed up: `netstat -tulpn | grep 8090` returns nothing
|
|
- [ ] `/opt/plane/` directory removed
|
|
- [ ] Nginx config removed: `ls /etc/nginx/sites-*/ | grep plane` returns nothing
|
|
- [ ] n8n workflows archived or deleted
|
|
- [ ] Documentation updated
|
|
|
|
---
|
|
task_number: 82
|
|
|
|
## Why Plane Didn't Fit
|
|
|
|
**Technical Success:**
|
|
- Deployment worked
|
|
- Projects created successfully
|
|
- Member invites sent
|
|
- Labels configured
|
|
|
|
**Workflow Mismatch:**
|
|
- Gitea's built-in Kanban boards proved simpler
|
|
- n8n sync integration was fragile (webhook loops)
|
|
- Added complexity without clear benefit
|
|
- Team already comfortable with Gitea workflow
|
|
|
|
**Decision:** Simplify stack, use Gitea Projects exclusively.
|
|
|
|
---
|
|
task_number: 82
|
|
|
|
## What Replaces Plane?
|
|
|
|
**Gitea Projects (Kanban Boards):**
|
|
- Native to our existing Git workflow
|
|
- No additional infrastructure
|
|
- No sync complexity
|
|
- Familiar interface for team
|
|
- Integrated with issues/PRs
|
|
|
|
---
|
|
task_number: 82
|
|
|
|
## Related Tasks
|
|
|
|
- Task #54: n8n Workflow Documentation (update to remove Plane workflows)
|
|
- None currently (Plane was isolated experiment)
|
|
|
|
---
|
|
task_number: 82
|
|
|
|
## Notes
|
|
|
|
- Plane data is not mission-critical (project tracking can be recreated in Gitea)
|
|
- No external dependencies to notify (internal tool only)
|
|
- DNS change may take 24-48 hours to propagate
|
|
- Consider what to do with `tasks.firefrostgaming.com` subdomain
|
|
|
|
---
|
|
task_number: 82
|
|
|
|
**Standard:** This task follows FFG-STD-002 (Task Documentation Standard)
|