Complete markdown files cleanup and organization

- Organized 252 files across project
- Root directory: 187 → 2 files (98.9% reduction)
- Moved configuration guides to docs/04-configuration/
- Moved troubleshooting guides to docs/09-troubleshooting/
- Moved quick start guides to docs/01-getting-started/
- Moved reports to reports/ directory
- Archived temporary files
- Generated comprehensive reports and documentation
- Created maintenance scripts and guides

All files organized according to established standards.
This commit is contained in:
defiQUG
2026-01-06 01:46:25 -08:00
parent 1edcec953c
commit cb47cce074
1327 changed files with 217220 additions and 801 deletions

View File

@@ -54,13 +54,23 @@ Create or update `~/.env` with Omada Controller credentials:
```bash
# Omada Controller Configuration
OMADA_CONTROLLER_URL=https://192.168.11.10:8043
OMADA_CONTROLLER_URL=https://192.168.11.8:8043
OMADA_API_KEY=your-client-id-here
OMADA_API_SECRET=your-client-secret-here
OMADA_SITE_ID=your-site-id # Optional - will use default site if not provided
OMADA_VERIFY_SSL=false # Set to true for production with valid SSL certs
```
**Note:** For automation and scripts, use the `proxmox-controller` API application (Client Credentials mode):
- Client ID: `94327608913c41bb9c32ce8d1d6e87d3`
- Client Secret: `600b924a541a4139a386cb7c63ac47b5`
For interactive access, use the `Datacenter-Control-Complete` API application (Authorization Code mode):
- Client ID: `8437ff7e3e39452294234ce23bbd105f`
- Client Secret: `f2d19e1bdcdd49adabe10f489ce09a79`
See the [Physical Hardware Inventory](../../config/physical-hardware-inventory.md) for complete API credential details.
### Finding Your Site ID
If you don't know your site ID:
@@ -168,7 +178,7 @@ import {
// Initialize client
const client = new OmadaClient({
baseUrl: 'https://192.168.11.10:8043',
baseUrl: 'https://192.168.11.8:8043',
clientId: process.env.OMADA_API_KEY!,
clientSecret: process.env.OMADA_API_SECRET!,
siteId: 'your-site-id',