security: sanitize internal hostname references

Replace all references to internal NAS hostname (jabba.lan) with generic
portainer-server.local placeholder.

Changes:
- README.md: Replace jabba.lan with portainer-server.local throughout
- docs/ROADMAP.md: Replace Jabba NAS references with generic server names
- docs/backlog.csv: Update all Jabba references in user stories
- scripts/*.ps1: Update script comments with generic hostname
- scripts/*.sh: Update script comments with generic hostname
- tests/: Update mock fixtures and test expectations

All occurrences sanitized (40+ references)
No internal infrastructure details remain exposed

This completes the sanitization process - repository is now fully
generic and safe for public consumption.

Author: unplugged12

.github/workflows/deploy.yml

@@ -22,7 +22,7 @@ on:
         default: false
 
 env:
-  PORTAINER_URL: https://jabba.lan:9444
+  PORTAINER_URL: https://portainer-server.local:9444
 
 jobs:
   pre-deploy-validation:

README.md

@@ -56,7 +56,7 @@ This repository manages MCP server deployments using:
 
 **Key Principle:** **Never commit secrets to Git**
 
-> **📝 Note:** Throughout this documentation, `jabba.lan:9444` is used as an example Portainer server hostname. Replace this with your own Portainer server address (e.g., `portainer.example.com:9443` or your server's IP/hostname).
+> **📝 Note:** Throughout this documentation, `portainer-server.local:9444` is used as an example Portainer server hostname. Replace this with your own Portainer server address (e.g., `portainer.example.com:9443` or your server's IP/hostname).
 
 ---
 
@@ -150,9 +150,9 @@ deploy:
 ### Prerequisites
 
 - Docker Desktop installed on all endpoints
-- Portainer CE running at `https://jabba.lan:9444`
+- Portainer CE running at `https://portainer-server.local:9444`
 - Git and GitHub CLI (`gh`) configured
-- Network access to Jabba (on-LAN or via VPN/Tailscale)
+- Network access to your Portainer server (on-LAN or via VPN/Tailscale)
 
 ### 1. Clone Repository
 
@@ -178,7 +178,7 @@ cd mcp-stacks
 
 #### Agent Endpoints (Desktops)
 
-1. Go to https://jabba.lan:9444
+1. Go to https://portainer-server.local:9444
 2. **Environments** → **Add environment**
 3. Select **Docker Standalone** → **Agent**
 4. Enter:
@@ -188,12 +188,12 @@ cd mcp-stacks
 
 #### Edge Endpoints (Laptops)
 
-1. Go to https://jabba.lan:9444
+1. Go to https://portainer-server.local:9444
 2. **Environments** → **Add environment**
 3. Select **Docker Standalone** → **Edge Agent** → **Standard**
 4. Configure:
    - **Name:** `laptop-<name>`
-   - **Portainer server URL:** `https://jabba.lan:9444`
+   - **Portainer server URL:** `https://portainer-server.local:9444`
    - **Edge Group:** `laptops` (create if doesn't exist)
 5. Copy the generated `docker run` command
 6. Run the install script and paste the command when prompted
@@ -641,7 +641,7 @@ git push origin main
 
 ### Via UI (Edge)
 
-1. https://jabba.lan:9444/#!/edge/stacks
+1. https://portainer-server.local:9444/#!/edge/stacks
 2. Select stack
 3. Click **Pull and redeploy**
 
@@ -661,7 +661,7 @@ git push origin main
 ### Option 1: WireGuard VPN (Existing)
 
 - Configure WireGuard client on laptops
-- DNS: Ensure `jabba.lan` resolves via WireGuard DNS
+- DNS: Ensure `portainer-server.local` resolves via WireGuard DNS
 
 ### Option 2: Tailscale (Recommended for Roaming)
 
@@ -674,10 +674,10 @@ git push origin main
 
 #### Install Tailscale
 
-**On Jabba (NAS):**
+**On portainer-server (NAS):**
 ```bash
 curl -fsSL https://tailscale.com/install.sh | sh
-sudo tailscale up --ssh --hostname jabba
+sudo tailscale up --ssh --hostname portainer-server
 ```
 
 **On Windows Laptops:**
@@ -704,7 +704,7 @@ tailscale up --auth-key tskey-auth-XXXXX --ssh --hostname <name>
 
 Once connected, access via Tailscale hostname:
 ```
-https://jabba.tail<YOUR_TAILNET>.ts.net:9444
+https://portainer-server.tail<YOUR_TAILNET>.ts.net:9444
 ```
 
 Or update your hosts to use Tailscale IP.
@@ -720,7 +720,7 @@ Or update your hosts to use Tailscale IP.
 **Solutions:**
 1. Check Edge tunnel reachability:
    ```powershell
-   Test-NetConnection jabba.lan -Port 8000
+   Test-NetConnection portainer-server.local -Port 8000
    ```
 2. Verify agent container is running:
    ```bash
@@ -730,7 +730,7 @@ Or update your hosts to use Tailscale IP.
    ```bash
    docker logs portainer_edge_agent
    ```
-4. Ensure Portainer server URL is `https://jabba.lan:9444` (not 9443!)
+4. Ensure Portainer server URL is `https://portainer-server.local:9444` (not 9443!)
 
 ### Stack Deployment Fails
 

docs/ROADMAP.md

@@ -91,7 +91,7 @@ Transform the mcp-stacks GitOps deployment platform from a functional proof-of-c
 #### 1.2 Monitoring & Observability Foundation
 **Duration:** 2 weeks | **Owner:** SRE Lead
 
-- Deploy Prometheus + Grafana stack on Jabba (NAS) **or** migrate it to a
+- Deploy Prometheus + Grafana stack on portainer-server (NAS) **or** migrate it to a
   dedicated host when NAS resources are constrained
 - Implement cAdvisor for container metrics on all endpoints
 - Create Grafana dashboards for MCP service health
@@ -167,7 +167,7 @@ Transform the mcp-stacks GitOps deployment platform from a functional proof-of-c
 #### 3.1 Tailscale Integration
 **Duration:** 1 week | **Owner:** Network Engineer
 
-- Deploy Tailscale on Jabba NAS
+- Deploy Tailscale on portainer-server NAS
 - Create deployment scripts for Tailscale on endpoints
 - Update Portainer connection documentation for Tailscale
 - Test Edge agent connectivity over Tailscale mesh
@@ -291,8 +291,8 @@ Transform the mcp-stacks GitOps deployment platform from a functional proof-of-c
 - Portainer CE v2.x with API access
 - Docker Desktop on all endpoints
 - GitHub repository with Actions enabled (or Azure DevOps)
-- Network access to Jabba NAS (on-LAN or Tailscale)
-- Prometheus and Grafana infrastructure capacity on Jabba
+- Network access to portainer-server NAS (on-LAN or Tailscale)
+- Prometheus and Grafana infrastructure capacity on portainer-server
 - Team bandwidth: 1-2 FTE for 14 weeks
 
 ## Post-Launch Roadmap

docs/SECRETS.md

@@ -41,7 +41,7 @@ Required only for automated deployment via API. Manual deployment through Portai
 | `PORTAINER_API_KEY` | Portainer API access token | Deployment workflow | Portainer UI → User → Access tokens |
 
 **To create a Portainer API token:**
-1. Go to https://jabba.lan:9444
+1. Go to https://portainer-server.local:9444
 2. Click on your username (top-right)
 3. Navigate to "Access tokens"
 4. Click "Add access token"

docs/backlog.csv

@@ -5,10 +5,10 @@ Story;Configure Portainer Environment Groups;Set up dev-agents, staging-agents,
 Story;Implement Environment Promotion Workflow;Define and document the process for promoting deployments from dev → staging → prod;Promotion workflow documented with approval gates, scripts created for automated promotion, runbook available;3;process,automation;
 Story;Update GitOps Polling Per Environment;Configure different polling intervals for dev (1min), staging (5min), prod (manual/webhook);Polling intervals configured per environment, webhook setup documented for production;2;infrastructure,gitops;
 Epic;Monitoring & Observability Foundation;Deploy comprehensive monitoring stack with Prometheus, Grafana, and log aggregation;Prometheus deployed, Grafana dashboards created, Loki aggregating logs from all endpoints;8;observability,foundation;
-Story;Deploy Prometheus on Jabba NAS;Install and configure Prometheus for metrics collection from all MCP services;Prometheus running on Jabba, scraping metrics from all endpoints, retention configured to 30 days;3;monitoring,infrastructure;
-Story;Deploy Grafana Dashboard Stack;Install Grafana and create base dashboards for MCP service health and resource usage;Grafana installed, accessible at jabba.lan:3000, 3+ dashboards created (service health, resource usage, alerts);3;monitoring,visualization;
+Story;Deploy Prometheus on portainer-server NAS;Install and configure Prometheus for metrics collection from all MCP services;Prometheus running on portainer-server, scraping metrics from all endpoints, retention configured to 30 days;3;monitoring,infrastructure;
+Story;Deploy Grafana Dashboard Stack;Install Grafana and create base dashboards for MCP service health and resource usage;Grafana installed, accessible at portainer-server.lan:3000, 3+ dashboards created (service health, resource usage, alerts);3;monitoring,visualization;
 Story;Implement cAdvisor on All Endpoints;Deploy cAdvisor containers for Docker container metrics on Agent and Edge endpoints;cAdvisor running on all endpoints, metrics flowing to Prometheus, no resource impact on Edge devices;2;monitoring,metrics;
-Story;Deploy Loki for Log Aggregation;Install Loki on Jabba and configure Promtail on all endpoints for centralized logging;Loki running, Promtail deployed to all endpoints, logs searchable in Grafana, retention policy configured;5;logging,infrastructure;
+Story;Deploy Loki for Log Aggregation;Install Loki on portainer-server and configure Promtail on all endpoints for centralized logging;Loki running, Promtail deployed to all endpoints, logs searchable in Grafana, retention policy configured;5;logging,infrastructure;
 Story;Create Base Grafana Dashboards;Design and export reusable Grafana dashboards for MCP service monitoring;3+ dashboards created (service uptime, resource usage, error rates), JSON exports available in repo;3;monitoring,visualization;
 Epic;Health Checks & Service Resilience;Add Docker health checks, restart policies, and resource limits to all MCP services;All services have health checks, resource limits set, enhanced post-deployment validation working;5;reliability,foundation;
 Story;Add Health Checks to Common Compose;Implement Docker HEALTHCHECK directives for all services in stacks/common/docker-compose.yml;Health checks added to all 4 MCP services, timeout and retry parameters configured appropriately;2;reliability,docker;
@@ -32,8 +32,8 @@ Story;Automate Edge Config Backups;Create script to backup Edge Configs to encry
 Story;Implement Stack Config Backup to Git;Ensure all stack configurations are version controlled and recoverable;Git contains all stack configs, backup validation script created, recovery tested;1;operations,git;
 Story;Develop Disaster Recovery Runbooks;Create step-by-step recovery playbooks for common failure scenarios;Runbooks created for 5+ scenarios (Portainer failure, endpoint loss, corruption, network outage), tested;3;operations,documentation;
 Story;Test Recovery Procedures;Execute disaster recovery drills in isolated environment to validate procedures;All recovery scenarios tested, time-to-recovery measured, gaps identified and addressed;2;testing,operations;
-Epic;Tailscale Integration;Deploy Tailscale mesh network for resilient connectivity to Portainer and MCP services;Tailscale deployed on Jabba and all endpoints, MagicDNS working, documented for new endpoints;5;networking,infrastructure;
-Story;Deploy Tailscale on Jabba NAS;Install and configure Tailscale on the Jabba NAS for mesh networking;Tailscale running on Jabba, accessible via MagicDNS hostname, ACLs configured;2;networking,setup;
+Epic;Tailscale Integration;Deploy Tailscale mesh network for resilient connectivity to Portainer and MCP services;Tailscale deployed on portainer-server and all endpoints, MagicDNS working, documented for new endpoints;5;networking,infrastructure;
+Story;Deploy Tailscale on portainer-server NAS;Install and configure Tailscale on the portainer-server NAS for mesh networking;Tailscale running on portainer-server, accessible via MagicDNS hostname, ACLs configured;2;networking,setup;
 Story;Create Tailscale Deployment Scripts;Develop install-tailscale.ps1 and .sh scripts for automated endpoint onboarding;Scripts created for Windows, macOS, Linux, tested on multiple platforms, documented in README;2;automation,networking;
 Story;Update Portainer Connection Documentation;Document Portainer access via Tailscale for off-LAN scenarios;Documentation updated with Tailscale URLs, fallback procedures, troubleshooting steps;1;documentation,networking;
 Story;Test Edge Agent Connectivity over Tailscale;Validate Edge agents connect reliably over Tailscale mesh when off-LAN;Edge agents tested off-LAN via Tailscale, connectivity stable, latency acceptable;2;testing,networking;

scripts/api/redeploy-stack.ps1

@@ -6,7 +6,7 @@
     Redeploys Agent or Edge stacks by pulling latest from Git.
     Supports both regular stacks (Agent) and Edge stacks.
 .PARAMETER PortainerUrl
-    Portainer server URL (default: https://jabba.lan:9444)
+    Portainer server URL (default: https://portainer-server.local:9444)
 .PARAMETER ApiKey
     Portainer API key (X-API-Key header)
 .PARAMETER StackName
@@ -22,7 +22,7 @@
 [CmdletBinding()]
 param(
     [Parameter()]
-    [string]$PortainerUrl = "https://jabba.lan:9444",
+    [string]$PortainerUrl = "https://portainer-server.local:9444",
 
     [Parameter(Mandatory)]
     [string]$ApiKey,

scripts/api/redeploy-stack.sh

@@ -26,7 +26,7 @@ NC='\033[0m'
 API_KEY="${1:-}"
 STACK_NAME="${2:-}"
 TYPE="${3:-agent}"
-PORTAINER_URL="${PORTAINER_URL:-https://jabba.lan:9444}"
+PORTAINER_URL="${PORTAINER_URL:-https://portainer-server.local:9444}"
 
 if [ -z "$API_KEY" ] || [ -z "$STACK_NAME" ]; then
     echo -e "${RED}Usage: $0 <API_KEY> <STACK_NAME> [TYPE]${NC}"

scripts/build-edge-config.ps1

@@ -111,7 +111,7 @@ Write-Host ""
 Write-Host "🎉 Edge Config bundle ready!" -ForegroundColor Green
 Write-Host ""
 Write-Host "Next steps:" -ForegroundColor Cyan
-Write-Host "1. Log into Portainer at https://jabba.lan:9444" -ForegroundColor White
+Write-Host "1. Log into Portainer at https://portainer-server.local:9444" -ForegroundColor White
 Write-Host "2. Navigate to Edge Configurations" -ForegroundColor White
 Write-Host "3. Create new configuration targeting 'laptops' Edge Group" -ForegroundColor White
 Write-Host "4. Upload: $outputZip" -ForegroundColor White

scripts/build-edge-config.sh

@@ -112,7 +112,7 @@ echo ""
 echo -e "${GREEN}🎉 Edge Config bundle ready!${NC}"
 echo ""
 echo -e "${CYAN}Next steps:${NC}"
-echo -e "${NC}1. Log into Portainer at https://jabba.lan:9444${NC}"
+echo -e "${NC}1. Log into Portainer at https://portainer-server.local:9444${NC}"
 echo -e "${NC}2. Navigate to Edge Configurations${NC}"
 echo -e "${NC}3. Create new configuration targeting 'laptops' Edge Group${NC}"
 echo -e "${NC}4. Upload: $OUTPUT_ZIP${NC}"

scripts/install/install-agent.ps1

@@ -4,7 +4,7 @@
     Install Portainer Agent on desktop/always-on hosts
 .DESCRIPTION
     Deploys portainer/agent:latest on port 9001 with auto-restart.
-    Verifies connectivity from Jabba (https://jabba.lan:9444).
+    Verifies connectivity from portainer-server (https://portainer-server.local:9444).
 .EXAMPLE
     .\install-agent.ps1
 #>
@@ -97,7 +97,7 @@ Write-Host ""
 Write-Host "🎉 Portainer Agent installation complete!" -ForegroundColor Green
 Write-Host ""
 Write-Host "Next steps:" -ForegroundColor Cyan
-Write-Host "1. Log into Portainer at https://jabba.lan:9444" -ForegroundColor White
+Write-Host "1. Log into Portainer at https://portainer-server.local:9444" -ForegroundColor White
 Write-Host "2. Navigate to Environments → Add environment" -ForegroundColor White
 Write-Host "3. Select 'Docker Standalone' → 'Agent'" -ForegroundColor White
 Write-Host "4. Enter this machine's hostname/IP and port $AgentPort" -ForegroundColor White