Files

Michael Schiemer 9b74ade5b0 feat: Fix discovery system critical issues

Resolved multiple critical discovery system issues:

## Discovery System Fixes
- Fixed console commands not being discovered on first run
- Implemented fallback discovery for empty caches
- Added context-aware caching with separate cache keys
- Fixed object serialization preventing __PHP_Incomplete_Class

## Cache System Improvements
- Smart caching that only caches meaningful results
- Separate caches for different execution contexts (console, web, test)
- Proper array serialization/deserialization for cache compatibility
- Cache hit logging for debugging and monitoring

## Object Serialization Fixes
- Fixed DiscoveredAttribute serialization with proper string conversion
- Sanitized additional data to prevent object reference issues
- Added fallback for corrupted cache entries

## Performance & Reliability
- All 69 console commands properly discovered and cached
- 534 total discovery items successfully cached and restored
- No more __PHP_Incomplete_Class cache corruption
- Improved error handling and graceful fallbacks

## Testing & Quality
- Fixed code style issues across discovery components
- Enhanced logging for better debugging capabilities
- Improved cache validation and error recovery

Ready for production deployment with stable discovery system.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

2025-08-13 12:04:17 +02:00

3.3 KiB

Raw Blame History

Deployment Backup Summary

This directory contains the old deployment configurations that were moved during the modernization of the deployment system.

Moved Directories

ansible/

Original Location: /ansible/
Contents: Multiple Ansible deployment configurations

netcup-simple-deploy/ - Basic server deployment setup
nginx-cdn-germany/ - CDN and Nginx configuration for German servers
wireguard-server/ - VPN server setup and client management

Key Features Preserved:

Server setup automation
Nginx reverse proxy configuration
SSL certificate management
Multi-environment support (staging/production)

x_ansible/

Original Location: /x_ansible/
Contents: Alternative Ansible setup with different structure

Complete playbook structure with inventories
Docker Compose integration
Environment-specific configurations
Deployment and setup scripts

ssl/

Original Location: /ssl/
Contents: SSL certificates and keys for local development

fullchain.pem - Certificate chain
privkey.pem - Private key
rootCA.* - Root certificate authority files
localhost.* - Local development certificates

Note: These certificates will be integrated into the new SSL management system in deployment/configs/ssl/

bin/

Original Location: /bin/
Contents: Deployment utility scripts

deploy - Environment-specific deployment script
setup - Server setup script
up, down, restart - Docker management scripts
logs, test, check-env - Utility scripts

Note: Functionality from these scripts will be modernized and integrated into deployment/scripts/

Migration Path

The new deployment system in /deployment/ consolidates and modernizes these configurations:

Infrastructure (/deployment/infrastructure/):
- Consolidates Ansible playbooks from both ansible/ directories
- Adds modern server configuration management
- Implements security best practices
Applications (/deployment/applications/):
- Modernizes Docker Compose configurations
- Adds environment-specific optimizations
- Integrates health checking and monitoring
Scripts (/deployment/scripts/):
- Modernizes and consolidates utility scripts from bin/
- Adds deployment orchestration capabilities
- Implements rollback and recovery features
Configs (/deployment/configs/):
- Centralizes configuration templates
- Integrates SSL certificate management
- Adds monitoring and logging configurations

Recovery Instructions

If you need to revert to the old deployment system:

Stop any new deployment processes

Move directories back from .deployment-backup/ to their original locations:

mv .deployment-backup/ansible ./
mv .deployment-backup/x_ansible ./  
mv .deployment-backup/ssl ./
mv .deployment-backup/bin ./

Update any references to the new deployment system

Preservation Notes

All original files are preserved unchanged
Directory structure maintained as-is
No modifications made to original configurations
Can be used for reference during new system development

Cleanup

Once the new deployment system is fully tested and deployed, this backup directory can be removed. Recommended timeline: Keep for at least 30 days after successful production deployment of the new system.

3.3 KiB Raw Blame History