Files
Jordan Ramos c4962194e3 feat(auth): integrate TinyAuth SSO for NetBox authentication
Deploy TinyAuth v4 as CT 115 (192.168.2.10) to provide centralized
SSO authentication for NetBox via Nginx Proxy Manager.

**New Infrastructure:**
- CT 115: TinyAuth authentication layer
- Domain: tinyauth.apophisnetworking.net
- Integration: NPM auth_request → TinyAuth → NetBox

**Configuration:**
- Docker Compose with bcrypt-hashed credentials
- NPM advanced config for auth_request integration
- HTTPS enforcement via SSL termination

**Issues Resolved:**
- 500 Internal Server Error (Nginx config syntax)
- "IP addresses not allowed" (APP_URL domain requirement)
- Port mapping (8000:3000 for internal port 3000)
- Invalid password (bcrypt hash requirement for v4)

**Documentation:**
- Complete TinyAuth README at services/tinyauth/README.md
- Updated CLAUDE_STATUS.md with CT 115 infrastructure
- Added bug report for scribe agent tool permissions

**Note:** Container restart required on CT 115 to apply bcrypt hash

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

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2025-12-18 08:15:05 -07:00

98 lines
2.6 KiB
Markdown

# Homelab Infrastructure Export
This directory contains a complete snapshot of your Proxmox-based homelab infrastructure, collected automatically via the homelab collection script.
## Collection Information
- **Collection Date**: 2025-12-11 14:43:55
- **Proxmox Node**: serviceslab
- **Collection Level**: standard
- **Sanitization Applied**: IPs=false, Passwords=true, Tokens=true
## Directory Structure
## Configuration Files
### Proxmox Core Configurations
- - Datacenter-wide settings
- - Storage pool definitions
- - User and permission configurations
- - Cluster-level firewall rules
### Virtual Machines
Each VM configuration is named:
Firewall rules (if present):
### LXC Containers
Each container configuration is named:
Firewall rules (if present):
## System Exports
### System Information
- Proxmox version, hostname, kernel info
- CPU, memory, and disk information
- Network configuration and routing
- Installed packages
### Cluster Information
- Cluster status and membership
- Resource allocation
- Recent tasks
### Guest Information
- List of all VMs and containers
- Resource usage and status
- JSON exports for programmatic access
## Security Notes
This export may contain sensitive information depending on sanitization settings:
- **Passwords**: true
- **API Tokens**: true
- **IP Addresses**: false
**Recommendation**: Store this export securely. Do not commit to public repositories without careful review.
## Using This Export
### As Documentation
These files serve as a snapshot of your infrastructure at a point in time. Use them for:
- Documentation and disaster recovery
- Change tracking (diff with previous exports)
- Migration planning
### Infrastructure as Code
Use the collected configurations to:
- Create Terraform/OpenTofu templates
- Build Ansible playbooks
- Document network architecture
### Restoration Reference
In a disaster recovery scenario:
1. Reinstall Proxmox VE
2. Reference storage configuration from
3. Reference network setup from
4. Recreate VMs/containers using configs in and
5. Restore VM disk images from backups
## Next Steps
1. **Review the SUMMARY.md** for collection statistics
2. **Check collection.log** for any warnings or errors
3. **Manually add documentation** to the folder
4. **Create network diagrams** and place in
5. **Version control** this export in a private Git repository
6. **Set up regular collections** to track infrastructure changes
## Collection Script
This export was created by the Homelab Infrastructure Collection Script.
For questions or issues, consult the script documentation.
---
*Generated by homelab-export-script v1.0.0*