diff --git a/databases/docker-compose.yml b/databases/docker-compose.yml
index 7eb1f48..ca8fa3b 100644
--- a/databases/docker-compose.yml
+++ b/databases/docker-compose.yml
@@ -27,20 +27,31 @@ services:
networks:
- db-net
+ # --- REDIS (New) ---
+ redis:
+ image: redis:alpine
+ container_name: redis
+ restart: always
+ # Note: Using 'Nyhjew-didvot-zypsa7' to stay consistent with your PG pass,
+ # or you can change this to a new one.
+ command: redis-server --requirepass "Nyhjew-didvot-zypsa7" --save 60 1
+ ports:
+ - "6379:6379"
+ volumes:
+ - ./redis-data:/data
+ networks:
+ - db-net
+
# --- KOMODO AGENT (PERIPHERY) ---
komodo-periphery:
image: ghcr.io/moghtech/komodo-periphery:2
container_name: komodo-periphery
restart: always
environment:
- # The Tailscale IP of VM1 (The Brain)
PERIPHERY_CORE_ADDRESS: 100.80.179.128:9120
- # The name that will appear in your Komodo Web UI
PERIPHERY_CONNECT_AS: Mystic-Databases
- # Your Onboarding Key from the UI
PERIPHERY_ONBOARDING_KEY: O_dPWwdaJNO7q87kgvPE4hnjaLlcsu_O
PERIPHERY_SERVER_ENABLED: "true"
- # Recommended for correct disk reporting
PERIPHERY_INCLUDE_DISK_MOUNTS: /etc/hostname
ports:
- "8120:8120"
@@ -51,7 +62,7 @@ services:
networks:
- db-net
- # --- MONITORING EXPORTERS (Scraped by VM1) ---
+ # --- MONITORING EXPORTERS ---
node-exporter:
image: prom/node-exporter:latest
container_name: node-exporter
@@ -80,7 +91,7 @@ services:
container_name: postgres-exporter
restart: always
environment:
- - DATA_SOURCE_NAME=postgresql://mystic_admin:your_secure_password@postgres:5432/postgres?sslmode=disable
+ - DATA_SOURCE_NAME=postgresql://mystic_admin:Nyhjew-didvot-zypsa7@postgres:5432/postgres?sslmode=disable
ports:
- "9187:9187"
networks:
@@ -97,6 +108,20 @@ services:
networks:
- db-net
+ redis-exporter:
+ image: oliver006/redis_exporter:latest
+ container_name: redis-exporter
+ restart: always
+ environment:
+ - REDIS_ADDR=redis://redis:6379
+ - REDIS_PASSWORD=Nyhjew-didvot-zypsa7
+ ports:
+ - "9121:9121"
+ depends_on:
+ - redis
+ networks:
+ - db-net
+
networks:
db-net:
driver: bridge
\ No newline at end of file
diff --git a/dns/docker-compose.yml b/dns/docker-compose.yml
new file mode 100644
index 0000000..eff8b92
--- /dev/null
+++ b/dns/docker-compose.yml
@@ -0,0 +1,49 @@
+services:
+ pihole:
+ container_name: pihole
+ image: pihole/pihole:latest
+ dns:
+ - 1.1.1.1
+ - 8.8.8.8
+ ports:
+ - "53:53/tcp"
+ - "53:53/udp"
+ - "80:80/tcp" # This is fine since Caddy isn't on this VM!
+ environment:
+ TZ: 'America/New_York'
+ WEBPASSWORD: 'dYtdyz-ginqas-pastu0'
+ PIHOLE_DNS_: '8.8.8.8;1.1.1.1'
+ DNSMASQ_LISTENING: 'all'
+ volumes:
+ - './etc-pihole:/etc/pihole'
+ - './etc-dnsmasq.d:/etc/dnsmasq.d'
+ restart: unless-stopped
+ cap_add:
+ - SYS_NICE
+
+ node-exporter:
+ image: prom/node-exporter:latest
+ container_name: node-exporter
+ ports:
+ - "9100:9100"
+
+ cadvisor:
+ image: gcr.io/cadvisor/cadvisor:latest
+ container_name: cadvisor
+ ports:
+ - "8080:8080"
+ volumes:
+ - /:/rootfs:ro
+ - /var/run:/var/run:ro
+ - /sys:/sys:ro
+ - /var/lib/docker/:/var/lib/docker:ro
+
+ pihole-exporter:
+ image: ekofr/pihole-exporter:latest
+ container_name: pihole-exporter
+ environment:
+ - PIHOLE_PROTOCOL=http
+ - PIHOLE_HOSTNAME=pihole
+ - PIHOLE_PASSWORD=dYtdyz-ginqas-pastu0
+ ports:
+ - "9617:9617"
\ No newline at end of file
diff --git a/git/docker-compose.yml b/git/docker-compose.yml
index 3303e52..f0e1ca9 100644
--- a/git/docker-compose.yml
+++ b/git/docker-compose.yml
@@ -11,10 +11,10 @@ services:
- FORGEJO__database__USER=forgejodb
- FORGEJO__database__PASSWD=Nyhjew-didvot-zypsa7 # Must match VM3 setup
- FORGEJO__metrics__ENABLED=true # Enables internal exporter
- - FORGEJO__metrics__TOKEN=mystic_metrics_token # Security for metrics
+ - FORGEJO__metrics__TOKEN=
ports:
- - "3000:3000"
- - "2222:22"
+ - "0.0.0.0:3000:3000" # Explicitly bind to all interfaces
+ - "0.0.0.0:2222:22"
volumes:
- ./data:/data
- /etc/timezone:/etc/timezone:ro
diff --git a/legal/html/privacy.html b/legal/html/privacy.html
new file mode 100644
index 0000000..e1699be
--- /dev/null
+++ b/legal/html/privacy.html
@@ -0,0 +1,62 @@
+
+
+
+
+
+ Privacy Policy | CoreBot Labs
+
+
+
+
Privacy Policy
+
Effective Date: April 1, 2026
+
+
1. Data Collection
+
To provide our Discord bot services, we collect the following information:
+
+
Discord User Data: User IDs, Server IDs, and Channel IDs.
+
Activity Metrics: We log that a message was sent, the length of the message, and total message counts per user. We do not log or store the text content of your messages.
+
System Metrics: Interaction metadata and infrastructure performance data are logged via our internal monitoring (Loki/Prometheus) to ensure service stability.
+
+
+
2. Data Usage
+
We use this information strictly to:
+
+
Power Bot features (e.g., user profiles and activity tracking).
+
Monitor the health and security of the CoreBot Labs infrastructure.
+
Facate user-requested data exports for external services.
+
+
+
3. Storage and Retention
+
+
Location: Data is hosted on secured servers in Canada and via Google Cloud (USA).
+
Discord User Data Retention: Personal data linked to Discord accounts is stored only as long as necessary to provide our services. This data is removed upon a verified request for deletion or if the service is no longer required.
+
System Metrics Retention: Non-identifiable system and server metrics are kept indefinitely for historical trend analysis, troubleshooting, and infrastructure optimization.
+
Deletion: You may request the removal of your Discord-related data at any time by contacting data@corebot.ca.
+
+
+
4. Data Sharing and Third Parties
+
+
No Sale of Data: CoreBot Labs does not sell your information.
+
Affiliates: We do not share user data with swvn.io, Nexus, or any other third parties.
+
Public Services: Use of vault.corebot.services is subject to the same strict non-disclosure standards.
+
+
+
5. Open Source Transparency
+
As an open-source project, our data handling logic is transparent and available for review at git.corebot.ca. Users running their own instances of CoreBot are responsible for their own data privacy compliance.
+
+
6. User Rights
+
Under GDPR and related privacy frameworks, you have the right to access, rectify, or request the deletion of your personal data. We support data portability and will provide data exports upon request via our support email.
+
+
+
+
\ No newline at end of file
diff --git a/legal/html/tos.html b/legal/html/tos.html
new file mode 100644
index 0000000..e5df915
--- /dev/null
+++ b/legal/html/tos.html
@@ -0,0 +1,46 @@
+
+
+
+
+
+ Terms of Service | CoreBot Labs
+
+
+
+
Terms of Service
+
Effective Date: April 1, 2026
+
+
1. Agreement to Terms
+
By adding CoreBot (the "Bot") to a Discord server or accessing CoreBot Labs infrastructure (the "Lab"), you agree to be bound by these Terms of Service. If you do not agree, please remove the Bot and cease use of our services.
+
+
2. Service Description
+
CoreBot Labs provides a Discord-integrated utility bot and related web services. We reserve the right to modify, suspend, or discontinue any aspect of the service at any time to maintain the stability of the Lab.
+
+
3. Open Source Licensing
+
While the CoreBot source code is available via git.corebot.ca under its respective open-source license, the "CoreBot Labs" name, branding, and hosted service instances (the Lab) remain the property of CoreBot Labs. Contributors are welcome, but CoreBot Labs is not responsible for third-party forks or self-hosted instances of the code.
+
+
4. License and Use
+
+
CoreBot Labs grants you a limited, non-exclusive license to use the Bot for its intended purposes.
+
Prohibited Use: You may not use the Bot for spam, "self-botting," or any action that disrupts the Lab’s performance or security.
+
Reverse Engineering: Unauthorized attempts to access the Lab's internal API or bypass security measures are strictly prohibited.
+
+
+
5. Affiliates
+
CoreBot is operated by CoreBot Labs (CB). While we maintain professional associations with swvn.io and Nexus, these are separate entities with their own terms and conditions.
+
+
6. Limitation of Liability
+
The Bot and all Lab services are provided "as-is." CoreBot Labs is not liable for any downtime, data loss, or damages resulting from the use of our services.