@lamalibre/create-lamaste 4.0.0

package/vendor/docs/05-operations/monitoring.md

@@ -0,0 +1,285 @@
+# Monitoring
+
+> Monitor your Lamaste server's health through the dashboard, service indicators, and live log streaming.
+
+## In Plain English
+
+Your Lamaste server is a small machine doing several jobs at once: routing web traffic, checking passwords, managing encrypted tunnels, and running the admin panel. Monitoring means keeping an eye on how hard the machine is working and whether all those jobs are running smoothly.
+
+Think of it like the dashboard in a car. You do not need to understand how the engine works to notice when a warning light comes on or the temperature gauge spikes. Lamaste gives you the same kind of dashboard for your server.
+
+## For Users
+
+### Dashboard Overview
+
+The **Dashboard** page is the first thing you see after logging into the management panel. It provides a real-time snapshot of your server's health across four key metrics.
+
+#### CPU Usage
+
+The CPU percentage tells you how much processing power is being used at this moment.
+
+| Range   | Meaning       | Action                      |
+| ------- | ------------- | --------------------------- |
+| 0-30%   | Normal idle   | None needed                 |
+| 30-60%  | Moderate load | Normal under traffic        |
+| 60-85%  | High load     | Investigate if sustained    |
+| 85-100% | Critical      | Check for runaway processes |
+
+On a single-vCPU $4 droplet, expect idle CPU around 2-5%. Brief spikes to 50-60% during certificate issuance or package updates are normal.
+
+#### Memory (RAM)
+
+Memory usage shows how much of the 512MB (or your droplet's total) is in use.
+
+**Expected baseline usage:**
+
+| Component            | Typical RAM |
+| -------------------- | ----------- |
+| OS (kernel, systemd) | ~120 MB     |
+| nginx                | ~15 MB      |
+| Authelia             | ~25 MB      |
+| Chisel               | ~20 MB      |
+| Panel (Node.js)      | ~30 MB      |
+| Fail2ban             | ~35 MB      |
+| **Total baseline**   | **~245 MB** |
+
+This leaves roughly 265 MB of headroom on a 512 MB droplet, plus a 1 GB swap file as a safety net.
+
+**Warning thresholds:**
+
+| Used % | Status   | Notes                               |
+| ------ | -------- | ----------------------------------- |
+| < 70%  | Normal   | Healthy headroom                    |
+| 70-85% | Elevated | Monitor trend                       |
+| 85-95% | Warning  | Check for memory leaks              |
+| > 95%  | Critical | Risk of OOM kills, check swap usage |
+
+If you see memory climbing steadily over days without returning to baseline, one of the services may have a memory leak. Restart the suspect service from the Services page and watch whether usage stabilizes.
+
+#### Disk Usage
+
+Disk usage reflects the root filesystem. On a fresh 25 GB droplet, Lamaste and its dependencies occupy roughly 2-3 GB.
+
+**Things that consume disk over time:**
+
+- Log files (journald, nginx access/error logs, Authelia logs)
+- Let's Encrypt certificate archives (small, but accumulate per domain)
+- Static site uploads under `/var/www/lamaste/`
+- Swap file (1 GB, fixed)
+
+**Warning thresholds:**
+
+| Used % | Status   | Action                                           |
+| ------ | -------- | ------------------------------------------------ |
+| < 70%  | Normal   | None                                             |
+| 70-85% | Watch    | Review log rotation                              |
+| 85-95% | Warning  | Clean old logs, remove unused sites              |
+| > 95%  | Critical | Free space immediately to avoid service failures |
+
+To check what is using disk space, SSH in and run:
+
+```bash
+sudo du -sh /var/log/* | sort -rh | head -10
+```
+
+#### Uptime
+
+System uptime shows how long the server has been running since its last reboot. Long uptimes (weeks or months) are normal and expected. The only reasons to reboot are kernel updates or hardware-level issues with the hosting provider.
+
+### Service Health Indicators
+
+The dashboard shows the status of each managed service:
+
+| Service  | Systemd Unit                | Role                                             |
+| -------- | --------------------------- | ------------------------------------------------ |
+| nginx    | `nginx`                     | Reverse proxy, TLS termination, mTLS enforcement |
+| Chisel   | `chisel`                    | WebSocket tunnel server                          |
+| Authelia | `authelia`                  | TOTP two-factor authentication                   |
+| Panel    | `lamalibre-lamaste-serverd` | Management API and UI                            |
+
+Each service displays one of these statuses:
+
+| Status     | Indicator | Meaning                                                 |
+| ---------- | --------- | ------------------------------------------------------- |
+| `active`   | Green     | Running normally                                        |
+| `inactive` | Gray      | Stopped (not started or manually stopped)               |
+| `failed`   | Red       | Crashed or failed to start                              |
+| `unknown`  | Gray      | Service not installed or systemd cannot determine state |
+
+Along with the status, each active service shows its **uptime** — how long it has been running since it was last started or restarted. If you see a service that recently restarted on its own (uptime much shorter than system uptime), check its logs for crash details.
+
+### Live Log Streaming
+
+The **Services** page lets you view live logs for any managed service. This uses a WebSocket connection to stream `journalctl` output directly to your browser.
+
+**How to use live logs:**
+
+1. Navigate to the **Services** page
+2. Click on a service name to expand it
+3. The log viewer opens and begins streaming the last 100 lines
+4. New log entries appear at the bottom in real time
+5. Close the viewer or navigate away to stop the stream
+
+**What the log entries look like:**
+
+Each log line contains an ISO timestamp and the log message:
+
+```
+2026-03-13T10:30:45+0000 droplet lamalibre-lamaste-serverd[1234]: Server listening on 127.0.0.1:3100
+2026-03-13T10:30:45+0000 droplet nginx[5678]: 203.0.113.42 - - [13/Mar/2026:10:30:45 +0000] "GET /api/health" 200
+```
+
+**Tips for reading logs:**
+
+- **nginx** logs show every HTTP request — useful for seeing who is connecting and what they are requesting
+- **chisel** logs show tunnel client connections and disconnections
+- **authelia** logs show authentication attempts, including failed TOTP entries
+- **lamalibre-lamaste-serverd** logs show API requests and any server-side errors
+
+### What Metrics to Watch
+
+For day-to-day monitoring, these are the most important signals:
+
+**Check daily (or set up external monitoring):**
+
+1. **All four services are active** — if any service is `failed`, investigate immediately
+2. **Memory usage is below 85%** — sustained high memory indicates a problem
+3. **Disk usage is below 85%** — running out of disk causes cascading failures
+
+**Check weekly:**
+
+1. **Certificate expiry dates** — the Certificates page shows days remaining. Let's Encrypt auto-renews at 30 days, but verify renewal is working
+2. **Disk growth trend** — if disk usage climbs steadily, investigate what is growing
+
+**Check after changes:**
+
+1. After adding a tunnel: verify the tunnel client connects (check Chisel logs)
+2. After adding a user: verify they can authenticate (check Authelia logs)
+3. After domain/DNS changes: verify certificates issued successfully (check Certificates page)
+
+## For Developers
+
+### System Stats API
+
+The dashboard fetches metrics from a single endpoint:
+
+```
+GET /api/system/stats
+```
+
+Response structure:
+
+```json
+{
+  "cpu": {
+    "usage": 3.2,
+    "cores": 1
+  },
+  "memory": {
+    "total": 536870912,
+    "used": 262144000,
+    "free": 274726912
+  },
+  "disk": {
+    "total": 26843545600,
+    "used": 3221225472,
+    "free": 23622320128
+  },
+  "uptime": 1234567
+}
+```
+
+Memory and disk values are in bytes. Uptime is in seconds. CPU usage is a percentage (0-100).
+
+The backend uses the `systeminformation` library with a 2-second cache to avoid excessive system calls when multiple clients poll simultaneously. The panel client polls this endpoint every 5 seconds via `react-query` (`refetchInterval: 5000`).
+
+### Service Status API
+
+```
+GET /api/services
+```
+
+Returns an array of service objects:
+
+```json
+{
+  "services": [
+    { "name": "nginx", "status": "active", "uptime": "5d 12h 30m" },
+    { "name": "chisel", "status": "active", "uptime": "5d 12h 28m" },
+    { "name": "authelia", "status": "active", "uptime": "5d 12h 28m" },
+    { "name": "lamalibre-lamaste-serverd", "status": "active", "uptime": "5d 12h 30m" }
+  ]
+}
+```
+
+The allowed service list is defined in `packages/lamaste-serverd/src/lib/services.js`:
+
+```
+nginx, chisel, authelia, lamalibre-lamaste-serverd
+```
+
+Service actions are available via:
+
+```
+POST /api/services/:name/:action
+```
+
+Where `action` is one of: `start`, `stop`, `restart`, `reload`.
+
+The panel prevents stopping `lamalibre-lamaste-serverd` from the UI, because that would terminate the session serving the request.
+
+### Live Log WebSocket
+
+The live log stream is available at:
+
+```
+WS /api/services/:name/logs
+```
+
+The server spawns `journalctl -u <service> -f -n 100 --output=short-iso` as a child process and pipes parsed lines to the WebSocket as JSON:
+
+```json
+{
+  "timestamp": "2026-03-13T10:30:45+0000",
+  "message": "droplet lamalibre-lamaste-serverd[1234]: Server listening on 127.0.0.1:3100"
+}
+```
+
+The server tracks all active `journalctl` processes and terminates them on WebSocket close, WebSocket error, or server shutdown to prevent orphaned processes.
+
+### External Monitoring
+
+For production use, consider setting up an external uptime monitor that hits your panel's health endpoint:
+
+```
+GET /api/health
+```
+
+This endpoint returns `200 OK` when the panel server is running. Since it is behind mTLS, your monitoring tool needs the client certificate, or you can monitor the IP:9292 HTTPS port for a valid TLS handshake.
+
+Alternatively, monitor the public-facing tunneled apps directly — if users can reach `https://myapp.example.com`, the full stack (nginx, Chisel, Authelia) is working.
+
+## Quick Reference
+
+| Metric         | Normal Range  | Warning          | Critical       |
+| -------------- | ------------- | ---------------- | -------------- |
+| CPU            | 0-30%         | 60-85% sustained | >85% sustained |
+| Memory         | <70% of total | 85-95%           | >95%           |
+| Disk           | <70% of total | 85-95%           | >95%           |
+| Service status | `active`      | `inactive`       | `failed`       |
+
+| API Endpoint                  | Method | Purpose                   |
+| ----------------------------- | ------ | ------------------------- |
+| `/api/system/stats`           | GET    | CPU, RAM, disk, uptime    |
+| `/api/services`               | GET    | All service statuses      |
+| `/api/services/:name/:action` | POST   | Start/stop/restart/reload |
+| `/api/services/:name/logs`    | WS     | Live log stream           |
+| `/api/health`                 | GET    | Health check              |
+
+| Log Command (SSH)                            | Purpose                 |
+| -------------------------------------------- | ----------------------- |
+| `journalctl -u nginx -f`                     | Follow nginx logs       |
+| `journalctl -u chisel -f`                    | Follow Chisel logs      |
+| `journalctl -u authelia -f`                  | Follow Authelia logs    |
+| `journalctl -u lamalibre-lamaste-serverd -f` | Follow panel logs       |
+| `journalctl -u nginx --since "1 hour ago"`   | Last hour of nginx logs |

package/vendor/docs/05-operations/uninstalling.md

@@ -0,0 +1,344 @@
+# Uninstalling
+
+> Completely remove Lamaste from your server, step by step.
+
+## In Plain English
+
+Uninstalling Lamaste means undoing everything the installer did: stopping the services, removing the files, deleting the user account, and optionally reverting the security hardening. After following this guide, your server will be as if Lamaste was never installed (except for system packages like nginx and Node.js, which you may want to keep).
+
+## For Users
+
+### Before You Begin
+
+1. **Download your backup** — if you might want to reinstall later, back up first (see [Backup and Restore](backup-and-restore.md))
+2. **Notify your users** — tunneled apps will become unreachable immediately after removal
+3. **SSH access** — you will need root SSH access to the server
+
+### Automated Removal
+
+`lamaste-server uninstall` performs the required steps below in one go (it asks for confirmation unless `--force` is passed):
+
+```bash
+sudo lamaste-server uninstall
+```
+
+It stops and disables the panel, gatekeeper, Chisel and Authelia; removes their systemd units, the sudoers file and the root-owned programs (`lamaste-priv`, `lamaste-certbot`, `lamaste-cert-info`, and the retired `lamaste-sign-csr` / `lamaste-pki-rename` if an older version left them); removes the Lamaste nginx vhosts and snippets, the Let's Encrypt certificates, `/etc/authelia`, `/var/log/authelia`, `/usr/local/bin/authelia`, `/usr/local/bin/chisel`, `/etc/lamalibre/lamaste`, `/var/www/lamaste`, `/opt/lamalibre/lamaste` and the global `@lamalibre/*` npm packages; and deletes the `lamaste` user, the `lamaste-chisel` group and the `lamaste-authelia` account. The optional steps (fail2ban, SSH, firewall, swap) are left to you.
+
+### Manual Removal
+
+The manual guide is also available from the CLI:
+
+```bash
+npx @lamalibre/create-lamaste@4.0.0 --uninstall
+```
+
+This prints the same steps listed below.
+
+### Step 1: Stop and Disable Services
+
+Stop all Lamaste-managed services so they do not restart on reboot:
+
+```bash
+sudo systemctl disable --now lamalibre-lamaste-serverd lamalibre-lamaste-gatekeeper chisel authelia
+```
+
+Remove the systemd unit files:
+
+```bash
+sudo rm -f /etc/systemd/system/{lamalibre-lamaste-serverd,lamalibre-lamaste-gatekeeper,chisel,authelia}.service
+sudo systemctl daemon-reload
+```
+
+**Verify:** No Lamaste services should appear as active:
+
+```bash
+systemctl list-units --type=service | grep -E 'lamaste|chisel|authelia'
+```
+
+Expected output: empty (no matching lines).
+
+### Step 2: Remove nginx Configuration
+
+Remove all Lamaste-related nginx vhosts and the mTLS snippet:
+
+```bash
+sudo rm -f /etc/nginx/sites-enabled/lamalibre-lamaste-*
+sudo rm -f /etc/nginx/sites-available/lamalibre-lamaste-*
+sudo rm -f /etc/nginx/snippets/lamalibre-lamaste-*
+```
+
+Test the remaining nginx configuration and reload:
+
+```bash
+sudo nginx -t && sudo systemctl reload nginx
+```
+
+If `nginx -t` fails, it means there are no remaining valid sites. You can either add back the default site or stop nginx entirely:
+
+```bash
+# Option A: Restore default site
+sudo ln -sf /etc/nginx/sites-available/default /etc/nginx/sites-enabled/default
+sudo nginx -t && sudo systemctl reload nginx
+
+# Option B: Stop nginx
+sudo systemctl stop nginx
+sudo systemctl disable nginx
+```
+
+### Step 3: Remove Lamaste Directories
+
+These directories contain all Lamaste configuration, state, and deployed files:
+
+```bash
+sudo rm -rf /etc/lamalibre/lamaste/       # Configuration, PKI certificates, state
+sudo rm -rf /opt/lamalibre/lamaste/       # Panel server and client files
+sudo rm -rf /var/www/lamaste/   # Static site files
+```
+
+**Warning:** This permanently deletes your PKI certificates. If you have not backed up `/etc/lamalibre/lamaste/pki/`, you will not be able to recover the client certificate or CA key.
+
+### Step 4: Remove Authelia Files
+
+```bash
+sudo rm -rf /etc/authelia/       # Authelia configuration, user database, SQLite database
+sudo rm -rf /var/log/authelia/   # Authelia log files
+```
+
+### Step 5: Remove Binaries
+
+Remove the Chisel and Authelia binaries and the root-owned programs the sudoers rules name:
+
+```bash
+sudo rm -f /usr/local/bin/chisel /usr/local/bin/authelia
+sudo rm -f /usr/local/sbin/lamaste-priv /usr/local/sbin/lamaste-certbot /usr/local/sbin/lamaste-cert-info
+```
+
+### Step 6: Remove the Service Accounts
+
+```bash
+sudo userdel -r lamaste
+sudo userdel lamaste-authelia
+sudo groupdel lamaste-chisel
+```
+
+The `-r` flag removes the home directory (if one exists). `lamaste` and `lamaste-authelia` are system users with no login shell, so there is nothing sensitive in their home directories.
+
+### Step 7: Remove Sudoers Rules
+
+```bash
+sudo rm -f /etc/sudoers.d/lamaste
+```
+
+**Verify:** Confirm the file is gone:
+
+```bash
+ls -la /etc/sudoers.d/lamaste
+```
+
+Expected: `No such file or directory`.
+
+### Step 8: Remove fail2ban Configuration (Optional)
+
+If you want to keep fail2ban running (recommended for security), skip this step. Only the Lamaste-specific jail configuration is removed:
+
+```bash
+sudo rm -f /etc/fail2ban/jail.d/lamaste.conf
+sudo systemctl restart fail2ban
+```
+
+### Step 9: Revert SSH Hardening (Optional)
+
+During installation, Lamaste hardens SSH by disabling password authentication. If a backup of the original configuration was created, you can restore it:
+
+```bash
+# Check if the backup exists
+ls -la /etc/ssh/sshd_config.pre-lamaste
+
+# Restore if it exists
+sudo cp /etc/ssh/sshd_config.pre-lamaste /etc/ssh/sshd_config
+sudo sshd -t && sudo systemctl restart ssh
+```
+
+**Warning:** Only revert SSH hardening if you understand the security implications. Disabling password authentication is a security best practice regardless of Lamaste.
+
+### Step 10: Revert Firewall Changes (Optional)
+
+Remove the Lamaste-specific UFW rule for port 9292:
+
+```bash
+sudo ufw delete allow 9292/tcp
+```
+
+Ports 22 (SSH) and 443 (HTTPS) were also opened during installation. You may want to keep these:
+
+```bash
+# Only remove if you no longer need HTTPS on this server
+sudo ufw delete allow 443/tcp
+```
+
+**Verify:**
+
+```bash
+sudo ufw status
+```
+
+### Step 11: Remove Swap File (Optional)
+
+If Lamaste created the swap file (common on 512 MB droplets):
+
+```bash
+sudo swapoff /swapfile
+sudo rm -f /swapfile
+```
+
+Remove the swap entry from `/etc/fstab`:
+
+```bash
+sudo sed -i '/\/swapfile/d' /etc/fstab
+```
+
+Remove the swappiness setting:
+
+```bash
+sudo rm -f /etc/sysctl.d/99-lamaste.conf
+sudo sysctl vm.swappiness=60  # Restore Ubuntu default
+```
+
+### Step 12: Remove Let's Encrypt Certificates (Optional)
+
+List all certificates managed by certbot:
+
+```bash
+sudo certbot certificates
+```
+
+Delete certificates for Lamaste domains:
+
+```bash
+# Replace with your actual domain
+sudo certbot delete --cert-name panel.example.com
+sudo certbot delete --cert-name auth.example.com
+sudo certbot delete --cert-name tunnel.example.com
+# Delete any app-specific certificates
+sudo certbot delete --cert-name myapp.example.com
+```
+
+### Step 13: Remove System Packages (Optional)
+
+If you installed this server solely for Lamaste and want to remove the system packages:
+
+```bash
+sudo apt-get remove --purge -y nginx certbot python3-certbot-nginx fail2ban
+sudo apt-get autoremove -y
+```
+
+**Warning:** Only do this if no other applications on this server depend on these packages.
+
+### Summary Checklist
+
+| Step                      | Command                                                                     | Required? |
+| ------------------------- | --------------------------------------------------------------------------- | --------- |
+| 1. Stop services          | `systemctl disable --now` + remove unit files                               | Yes       |
+| 2. Remove nginx config    | `rm lamalibre-lamaste-*` vhosts and snippets                                | Yes       |
+| 3. Remove Lamaste dirs    | `rm -rf /etc/lamalibre/lamaste/ /opt/lamalibre/lamaste/ /var/www/lamaste/`  | Yes       |
+| 4. Remove Authelia files  | `rm -rf /etc/authelia/ /var/log/authelia/`                                  | Yes       |
+| 5. Remove binaries        | `rm /usr/local/bin/{chisel,authelia}`, `/usr/local/sbin/lamaste-*`          | Yes       |
+| 6. Remove accounts        | `userdel -r lamaste`, `userdel lamaste-authelia`, `groupdel lamaste-chisel` | Yes       |
+| 7. Remove sudoers         | `rm /etc/sudoers.d/lamaste`                                                 | Yes       |
+| 8. Remove fail2ban config | `rm /etc/fail2ban/jail.d/lamaste.conf`                                      | Optional  |
+| 9. Revert SSH hardening   | Restore `sshd_config.pre-lamaste`                                           | Optional  |
+| 10. Revert firewall       | `ufw delete allow 9292/tcp`                                                 | Optional  |
+| 11. Remove swap           | `swapoff /swapfile && rm /swapfile`                                         | Optional  |
+| 12. Remove LE certs       | `certbot delete --cert-name <domain>`                                       | Optional  |
+| 13. Remove packages       | `apt-get remove nginx certbot fail2ban`                                     | Optional  |
+
+## For Developers
+
+### What the Installer Creates
+
+For reference, here is a complete list of everything the installer and onboarding provisioning create on the system:
+
+**Systemd services** (all written by the installer):
+
+- `/etc/systemd/system/lamalibre-lamaste-serverd.service`
+- `/etc/systemd/system/lamalibre-lamaste-gatekeeper.service`
+- `/etc/systemd/system/chisel.service`
+- `/etc/systemd/system/authelia.service`
+
+**Directories:**
+
+- `/etc/lamalibre/lamaste/` (config, state)
+- `/etc/lamalibre/lamaste/pki/` (certificates)
+- `/opt/lamalibre/lamaste/` (panel server, CLI, client, docs, gatekeeper — root-owned)
+- `/opt/lamalibre/lamaste/lamaste-serverd/` (Fastify backend)
+- `/opt/lamalibre/lamaste/lamaste-server-ui/` (React frontend build)
+- `/var/www/lamaste/` (static site uploads)
+- `/etc/authelia/` (auth config and user database)
+- `/var/log/authelia/` (auth logs)
+
+**Binaries** (installed by the installer):
+
+- `/usr/local/bin/chisel` (pinned release)
+- `/usr/local/bin/authelia` (pinned release)
+- `/usr/local/bin/lamaste-server` (symlink to the CLI)
+- `/usr/local/sbin/lamaste-priv`, `/usr/local/sbin/lamaste-certbot`, `/usr/local/sbin/lamaste-cert-info`
+
+**nginx files:**
+
+- `/etc/nginx/sites-available/lamalibre-lamaste-panel-ip`
+- `/etc/nginx/sites-available/lamalibre-lamaste-http-redirect`
+- `/etc/nginx/sites-available/lamalibre-lamaste-panel-domain`
+- `/etc/nginx/sites-available/lamalibre-lamaste-auth`
+- `/etc/nginx/sites-available/lamalibre-lamaste-tunnel`
+- `/etc/nginx/sites-available/lamalibre-lamaste-app-*`
+- `/etc/nginx/sites-available/lamalibre-lamaste-site-*`
+- `/etc/nginx/sites-available/lamalibre-lamaste-agent-panel-*`
+- Corresponding symlinks in `/etc/nginx/sites-enabled/`
+- `/etc/nginx/snippets/lamalibre-lamaste-mtls.conf`, `lamalibre-lamaste-authz-cache.conf`
+
+**System configuration:**
+
+- `/etc/sudoers.d/lamaste`
+- `/etc/fail2ban/jail.d/lamaste.conf`
+- `/etc/ssh/sshd_config.pre-lamaste` (backup only)
+- `/etc/sysctl.d/99-lamaste.conf`
+- `/swapfile` (and entry in `/etc/fstab`)
+
+**Service accounts:**
+
+- `lamaste` (system user, no login shell — runs the panel and gatekeeper)
+- `lamaste-authelia` (system user, no login shell, no home — runs Authelia)
+- `lamaste-chisel` (group — Chisel runs as `nobody:lamaste-chisel`; `lamaste` is a member)
+
+## Quick Reference
+
+**Quick uninstall (required steps only):**
+
+```bash
+sudo lamaste-server uninstall
+```
+
+Or by hand:
+
+```bash
+# Stop and remove services
+sudo systemctl disable --now lamalibre-lamaste-serverd lamalibre-lamaste-gatekeeper chisel authelia
+sudo rm -f /etc/systemd/system/{lamalibre-lamaste-serverd,lamalibre-lamaste-gatekeeper,chisel,authelia}.service
+sudo systemctl daemon-reload
+
+# Remove nginx config
+sudo rm -f /etc/nginx/sites-enabled/lamalibre-lamaste-*
+sudo rm -f /etc/nginx/sites-available/lamalibre-lamaste-*
+sudo rm -f /etc/nginx/snippets/lamalibre-lamaste-*
+sudo nginx -t && sudo systemctl reload nginx
+
+# Remove files, binaries, accounts, and sudoers
+sudo rm -rf /etc/lamalibre/lamaste/ /opt/lamalibre/lamaste/ /var/www/lamaste/
+sudo rm -rf /etc/authelia/ /var/log/authelia/
+sudo rm -f /usr/local/bin/chisel /usr/local/bin/authelia
+sudo rm -f /usr/local/sbin/lamaste-priv /usr/local/sbin/lamaste-certbot /usr/local/sbin/lamaste-cert-info
+sudo userdel -r lamaste
+sudo userdel lamaste-authelia
+sudo groupdel lamaste-chisel
+sudo rm -f /etc/sudoers.d/lamaste
+```