jbeasley/openclaw-workspace-2026
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
93b21a81642a5579ad5ea3ecb89eabd90faa55eb
openclaw-workspace-2026/COMPLETE_APPLICATIONS_INVENTORY.md
T
JC Beasley cb5e26b561 Update memory service with working NocoDB configuration 
- Set correct table ID: mx149yctebfwvys (ai_data_Memory)
- Updated type column with SingleSelect options
- Added all required columns for corrections, preferences, episodes, decisions, validation
- Fixed column options for type, severity, status fields
2026-07-04 17:02:40 -07:00

9.4 KiB
Raw Blame History

Complete Applications Inventory - 192.168.50.11

Overview

This document provides a comprehensive inventory of ALL applications found on the server at 192.168.50.11, including their locations, structure, and current status.

Running Applications (Currently Active)

1. IT Site Survey AI Application

  • Location: /home/jcbeasley/.openclaw/workspace/Projects/site-survey-ai/
  • Port: 3003
  • Process ID: 14287
  • Entry Point: app.py
  • Framework: Flask
  • Status: ✅ Running

2. Client Onboarding Application (Duplicate)

  • Location 1: /home/jcbeasley/Projects/client-onboarding/
  • Location 2: /home/jcbeasley/.openclaw/workspace/Projects/client-onboarding/
  • Port: 5000
  • Process ID: 318
  • Entry Point: app.py
  • Framework: Flask
  • Status: ✅ Running

3. Projects Manager Application (D.U.M.A APPS DASHBOARD)

  • Location: /home/jcbeasley/projects-manager/
  • Port: 3456
  • Process ID: 236
  • Entry Point: app.py
  • Framework: Flask
  • Status: ✅ Running

Non-Running Applications (Found on Server)

4. IT Assessment AI Application

  • Location: /home/jcbeasley/.openclaw/workspace/Projects/it-assessment-ai/
  • Entry Point: app.py
  • Framework: Flask
  • Status: ⏸️ Not Running

5. Dark Web Monitor Application

  • Location: /home/jcbeasley/Projects/dark-web-monitor/
  • Entry Point: (Unknown - needs investigation)
  • Framework: (Unknown)
  • Status: ⏸️ Not Running

6. Shorts Analyzer Application

  • Location 1: /home/jcbeasley/Projects/shorts-analyzer/
  • Location 2: /home/jcbeasley/.openclaw/workspace/Projects/shorts-analyzer/
  • Entry Point: server.py
  • Framework: (Unknown)
  • Status: ⏸️ Not Running

7. IT Assessment Static Site

  • Location: /home/jcbeasley/it-assessment/
  • Entry Point: index.html
  • Framework: Static HTML
  • Status: ⏸️ Not Running

8. Projects Manager Hosting Module

  • Location: /home/jcbeasley/projects-manager/hosting/
  • Entry Point: server.py
  • Framework: (Unknown)
  • Status: ⏸️ Not Running (Part of main Projects Manager)

Application Details

Running Applications

IT Site Survey AI (/home/jcbeasley/.openclaw/workspace/Projects/site-survey-ai/)

  • Files: app.py (792 lines), index.html, dashboard.html, concise_template.json
  • Storage: In-memory (surveys_db, survey_responses_db)
  • External Services: Ollama AI at http://192.168.19.25:11434
  • Key Features: Survey creation, AI analysis, PDF export, dashboard

Client Onboarding (/home/jcbeasley/.openclaw/workspace/Projects/client-onboarding/)

  • Files: app.py (~8,722 lines), dashboard/
  • Storage: In-memory (clients_db)
  • Key Features: Client account creation, checklist management

Projects Manager (/home/jcbeasley/projects-manager/)

  • Files: app.py (~77,034 lines), hosting/
  • Key Features: Projects dashboard, hosting management, VM provisioning
  • Note: Also contains hosting/server.py

Non-Running Applications

IT Assessment AI (/home/jcbeasley/.openclaw/workspace/Projects/it-assessment-ai/)

  • Files: app.py (needs size check)
  • Status: Not currently running

Dark Web Monitor (/home/jcbeasley/Projects/dark-web-monitor/)

  • Files: (needs investigation)
  • Status: Not currently running

Shorts Analyzer (/home/jcbeasley/.openclaw/workspace/Projects/shorts-analyzer/)

  • Files: server.py, other files (needs investigation)
  • Status: Not currently running

IT Assessment Static Site (/home/jcbeasley/it-assessment/)

  • Files: index.html (88,750 bytes)
  • Status: Static site, not running as service

Directory Structure Issues

1. Duplicate Applications

  • Client Onboarding: Exists in both /home/jcbeasley/Projects/ and /home/jcbeasley/.openclaw/workspace/Projects/
  • Shorts Analyzer: Exists in both locations
  • Risk: Confusion about which version is active

2. Inconsistent Organization

  • Some applications in /home/jcbeasley/Projects/
  • Some applications in /home/jcbeasley/.openclaw/workspace/Projects/
  • Some applications in /home/jcbeasley/ root directories
  • Risk: Difficulty in maintenance and updates

3. Mixed Application Types

  • Flask applications
  • Static HTML sites
  • Python scripts
  • Risk: Inconsistent deployment and management

Current Server State

Active Processes

  • 3 Flask applications running on ports 3003, 3456, 5000
  • All started with nohup for persistence
  • No zombie processes (except one defunct process PID 947)

Port Usage

  • 3003: IT Site Survey AI
  • 3456: Projects Manager
  • 5000: Client Onboarding

Storage Issues

  • All running applications use in-memory storage
  • Data loss on application restart
  • No database persistence

Database Status

  • PostgreSQL: Not installed
  • SQLite: Available but not used
  • Migration Required: Critical for all applications

Proposed Organization Structure

Standard Application Directory

/home/jcbeasley/applications/
├── active/                    # Currently running applications
│   ├── it-site-survey-ai/    # Port 3003
│   ├── client-onboarding/    # Port 5000
│   └── projects-manager/     # Port 3456
├── archived/                 # Old/backup applications
├── development/              # Applications in development
└── templates/                # Standard templates

Individual Application Structure

{application-name}/
├── src/                      # Source code
│   ├── app.py               # Application entry point
│   ├── config.py            # Configuration
│   ├── models/              # Data models
│   ├── api/                 # API endpoints
│   ├── services/            # Business logic
│   └── utils/               # Utility functions
├── frontend/                # Frontend assets
│   ├── static/              # CSS, JS, images
│   └── templates/           # HTML templates
├── tests/                   # Test files
├── docs/                    # Documentation
├── requirements/            # Dependencies
├── scripts/                 # Utility scripts
├── .env.example            # Environment examples
├── .gitignore
├── Dockerfile
├── README.md
└── Makefile

Backup and Restore Strategy

Pre-Organization Backup

  1. Complete Server Backup: Full backup of /home/jcbeasley/
  2. Application-Specific Backups: Individual backups of each application
  3. Configuration Backups: Backup of all running process configurations
  4. Database Backup: Preparation for future database migration

Restore Points

  1. Full Server Snapshot: Point-in-time snapshot before reorganization
  2. Application Snapshots: Individual application state backups
  3. Process Configuration: Running process configurations
  4. Data Exports: Export of current in-memory data

Implementation Plan

Phase 1: Assessment and Backup (1-2 days)

  1. Complete Inventory: Document all applications and their states
  2. Size Analysis: Check file sizes and dependencies
  3. Full Backup: Create complete server backup
  4. Running Process Backup: Document all running processes

Phase 2: Consolidation (2-3 days)

  1. Remove Duplicates: Consolidate duplicate applications
  2. Standard Directory Creation: Create /home/jcbeasley/applications/
  3. Application Migration: Move applications to standard structure
  4. Process Update: Update running process configurations

Phase 3: Standardization (3-4 days)

  1. Structure Implementation: Apply standard structure to each application
  2. Code Modularization: Split monolithic files into modules
  3. Testing Setup: Add test frameworks to all applications
  4. Documentation: Create documentation for each application

Phase 4: Validation (1-2 days)

  1. Functionality Testing: Verify all applications still work
  2. Process Verification: Ensure all processes start correctly
  3. Data Integrity: Verify no data loss during migration
  4. Performance Testing: Ensure no performance degradation

Risk Mitigation

1. Zero Downtime

  • Staged Migration: Move applications one at a time
  • Parallel Testing: Test new structure alongside old
  • Quick Rollback: Ability to revert to previous state immediately

2. Data Protection

  • Complete Backups: Full server state before any changes
  • Data Export: Export all in-memory data before migration
  • Verification: Verify data integrity after migration

3. Process Safety

  • Process Documentation: Document all running processes before changes
  • Configuration Backup: Backup all process configurations
  • Restore Scripts: Create automated restore procedures

Next Steps

Immediate Actions

  1. Complete Inventory: Finish documenting all applications
  2. Size Analysis: Check file sizes for all applications
  3. Backup Creation: Start full server backup process
  4. Process Documentation: Document all running processes in detail

Team Tasks to Add

  1. Server Organization - High Priority
  2. Application Consolidation - High Priority
  3. Structure Standardization - High Priority
  4. Backup and Restore Implementation - Critical Priority

This comprehensive inventory will enable proper organization of all applications on the server while ensuring zero code breakage and full restore capability.

Reference in New Issue View Git Blame Copy Permalink