Updates to Uptime Kuma monitoring setup: DNS Configuration: - Added DNS A record for status.vrije.cloud -> 94.130.231.155 - Updated Uptime Kuma container to use status.vrije.cloud domain - HTTPS access via nginx-proxy with Let's Encrypt SSL Automated Monitor Management: - Created scripts/add-client-to-monitoring.sh - Created scripts/remove-client-from-monitoring.sh - Integrated monitoring into deploy-client.sh (step 5/5) - Integrated monitoring into destroy-client.sh (step 0/7) - Deployment now prompts to add monitors after success - Destruction now prompts to remove monitors before deletion Email Notification Setup: - Created docs/uptime-kuma-email-setup.md with complete guide - SMTP configuration using smtp.strato.com - Credentials: server@postxsociety.org - Alerts sent to mail@postxsociety.org Documentation: - Updated docs/monitoring.md with new domain - Added email setup reference - Replaced all URLs to use status.vrije.cloud Benefits: ✅ Friendly domain instead of IP address ✅ HTTPS access with auto-SSL ✅ Automated monitoring reminders on deploy/destroy ✅ Complete email notification guide ✅ Streamlined workflow for monitor management Note: Monitor creation/deletion currently manual (API automation planned) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
56 lines
1.6 KiB
Bash
Executable file
56 lines
1.6 KiB
Bash
Executable file
#!/usr/bin/env bash
|
|
#
|
|
# Remove client monitors from Uptime Kuma
|
|
#
|
|
# Usage: ./scripts/remove-client-from-monitoring.sh <client_name>
|
|
#
|
|
# This script removes HTTP(S) and SSL monitors for a destroyed client
|
|
# Currently uses manual instructions - future: use Uptime Kuma API
|
|
|
|
set -euo pipefail
|
|
|
|
# Colors for output
|
|
RED='\033[0;31m'
|
|
GREEN='\033[0;32m'
|
|
YELLOW='\033[1;33m'
|
|
BLUE='\033[0;34m'
|
|
NC='\033[0m' # No Color
|
|
|
|
# Script directory
|
|
SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
|
|
PROJECT_ROOT="$(dirname "$SCRIPT_DIR")"
|
|
|
|
# Check arguments
|
|
if [ $# -ne 1 ]; then
|
|
echo -e "${RED}Error: Client name required${NC}"
|
|
echo "Usage: $0 <client_name>"
|
|
exit 1
|
|
fi
|
|
|
|
CLIENT_NAME="$1"
|
|
|
|
echo -e "${BLUE}========================================${NC}"
|
|
echo -e "${BLUE}Remove Client from Monitoring${NC}"
|
|
echo -e "${BLUE}========================================${NC}"
|
|
echo ""
|
|
echo -e "${YELLOW}Client: ${CLIENT_NAME}${NC}"
|
|
echo ""
|
|
|
|
# TODO: Implement automated monitor removal via Uptime Kuma API
|
|
# For now, provide manual instructions
|
|
|
|
echo -e "${YELLOW}Manual Removal Required:${NC}"
|
|
echo ""
|
|
echo "Please remove the following monitors from Uptime Kuma:"
|
|
echo "🔗 Access: https://status.vrije.cloud"
|
|
echo ""
|
|
echo "Monitors to delete:"
|
|
echo " • ${CLIENT_NAME} - Authentik"
|
|
echo " • ${CLIENT_NAME} - Nextcloud"
|
|
echo " • ${CLIENT_NAME} - Authentik SSL"
|
|
echo " • ${CLIENT_NAME} - Nextcloud SSL"
|
|
echo ""
|
|
echo -e "${BLUE}========================================${NC}"
|
|
echo ""
|
|
echo -e "${YELLOW}Note: Automated monitor removal via API is planned for future enhancement.${NC}"
|
|
echo ""
|