Add Oracle deployment assets and alerts ping

README.md

@@ -93,3 +93,24 @@ The `/bulkadd` modal accepts one bet per line in this format:
 Bryan Rocchio 1+ HR | +1450 | $5
 3 leg parlay | +1452 | $5
 ```
+
+## Oracle Cloud Always Free Deployment
+
+This bot is a good fit for an Oracle Cloud Always Free Ubuntu VM because it:
+
+- runs on Node.js `24+`
+- uses your remote CockroachDB/Postgres-compatible database
+- does not require local persistent bet storage
+
+Recommended deployment shape:
+
+- Oracle Compute VM with Ubuntu LTS
+- native Node runtime
+- `systemd` for auto-restart and boot persistence
+- SSH exposed publicly on port `22` only
+
+Deployment assets included in this repo:
+
+- `docs/oracle-always-free.md`
+- `deploy/oracle/roibot.service`
+- `deploy/oracle/roibot.env.example`

deploy/oracle/roibot.env.example

@@ -0,0 +1,5 @@
+DISCORD_TOKEN=your_discord_bot_token_here
+DATABASE_URL=postgresql://username:password@host:26257/database?sslmode=require
+GUILD_ID=optional_guild_id_for_faster_command_registration
+ADMIN_ROLE_NAME=Admin
+PORT=7860

deploy/oracle/roibot.service

@@ -0,0 +1,18 @@
+[Unit]
+Description=ROI Bet Tracking Discord Bot
+After=network-online.target
+Wants=network-online.target
+
+[Service]
+Type=simple
+User=roibot
+Group=roibot
+WorkingDirectory=/opt/roibot
+EnvironmentFile=/etc/roibot/roibot.env
+ExecStart=/usr/bin/node /opt/roibot/src/index.js
+Restart=always
+RestartSec=5
+TimeoutStopSec=20
+
+[Install]
+WantedBy=multi-user.target

docs/oracle-always-free.md

@@ -0,0 +1,174 @@
+# Oracle Cloud Always Free Deployment
+
+This bot runs well on an Oracle Cloud Always Free Ubuntu VM because it only needs:
+
+- Node.js `24+`
+- outbound internet access to Discord and CockroachDB
+- your existing `DATABASE_URL`
+
+The app does **not** need local persistent storage for bet history because the database is remote.
+
+## Recommended shape
+
+- OS: Ubuntu LTS
+- Runtime: native Node.js, not Docker
+- Service manager: `systemd`
+- Public inbound ports: `22/tcp` only
+- Preferred instance: AMD micro if available
+- Fallback instance: Ampere ARM if AMD capacity is unavailable
+
+## 1. Create the Oracle VM
+
+Create an Oracle Compute instance in your home region:
+
+- image: Ubuntu LTS
+- public IP: yes
+- ingress: allow `22/tcp` only
+- leave outbound internet access enabled
+
+Do not expose port `7860` publicly. The health server can stay local to the VM.
+
+## 2. SSH into the VM
+
+Replace `YOUR_PUBLIC_IP` with the VM's public IP:
+
+```bash
+ssh ubuntu@YOUR_PUBLIC_IP
+```
+
+## 3. Bootstrap the machine
+
+Update packages and install the basics:
+
+```bash
+sudo apt-get update
+sudo apt-get upgrade -y
+sudo apt-get install -y git curl build-essential ca-certificates
+```
+
+Install Node.js 24:
+
+```bash
+curl -fsSL https://deb.nodesource.com/setup_24.x | sudo -E bash -
+sudo apt-get install -y nodejs
+node -v
+npm -v
+```
+
+## 4. Create the bot user and folders
+
+```bash
+sudo useradd --system --create-home --shell /bin/bash roibot
+sudo mkdir -p /opt/roibot
+sudo mkdir -p /etc/roibot
+sudo chown -R roibot:roibot /opt/roibot
+```
+
+## 5. Clone the repo
+
+If the repo is private, use your preferred authenticated Git workflow.
+
+```bash
+sudo -u roibot git clone https://huggingface.co/spaces/Syntrex/ROIBot /opt/roibot
+cd /opt/roibot
+sudo -u roibot npm install
+```
+
+## 6. Create the runtime env file
+
+Copy the example from `deploy/oracle/roibot.env.example` into `/etc/roibot/roibot.env`:
+
+```bash
+sudo cp /opt/roibot/deploy/oracle/roibot.env.example /etc/roibot/roibot.env
+sudo nano /etc/roibot/roibot.env
+```
+
+Set:
+
+- `DISCORD_TOKEN`
+- `DATABASE_URL`
+- `GUILD_ID` if you want faster command sync in a single server
+- `ADMIN_ROLE_NAME=Admin`
+- `PORT=7860`
+
+Lock down the file:
+
+```bash
+sudo chown roibot:roibot /etc/roibot/roibot.env
+sudo chmod 600 /etc/roibot/roibot.env
+```
+
+## 7. Smoke test manually
+
+Run the bot once before wiring `systemd`:
+
+```bash
+cd /opt/roibot
+sudo -u roibot env $(cat /etc/roibot/roibot.env | xargs) node src/index.js
+```
+
+You want to see:
+
+- database initialized successfully
+- Discord login succeeds
+- slash commands register
+
+Stop it with `Ctrl+C` after confirming startup.
+
+## 8. Install the systemd service
+
+Copy the included service file:
+
+```bash
+sudo cp /opt/roibot/deploy/oracle/roibot.service /etc/systemd/system/roibot.service
+sudo systemctl daemon-reload
+sudo systemctl enable roibot
+sudo systemctl start roibot
+```
+
+Check status:
+
+```bash
+sudo systemctl status roibot
+sudo journalctl -u roibot -n 100 --no-pager
+```
+
+## 9. Verify the bot is online
+
+Check in Discord that:
+
+- the bot appears online
+- `/bet` works
+- `/summary` works
+- restricted commands such as `/welcome` still behave correctly
+
+## 10. Update workflow
+
+When you deploy a new version:
+
+```bash
+ssh ubuntu@YOUR_PUBLIC_IP
+cd /opt/roibot
+sudo -u roibot git pull
+sudo -u roibot npm install
+sudo systemctl restart roibot
+sudo systemctl status roibot
+sudo journalctl -u roibot -n 100 --no-pager
+```
+
+## 11. Recovery checks
+
+If the bot goes offline:
+
+```bash
+sudo systemctl status roibot
+sudo journalctl -u roibot -n 200 --no-pager
+```
+
+If Oracle reboots the VM, `systemd` should bring the bot back automatically.
+
+## AMD vs Ampere notes
+
+- AMD micro is the least fussy option when free capacity is available.
+- Ampere ARM is also valid for this bot if AMD capacity is unavailable.
+- The same Node.js and `systemd` setup works for both; just use the standard Ubuntu Node 24 installation flow.

src/index.js

@@ -772,9 +772,14 @@ async function handleAlerts(interaction) {
     components: buildAlertsButtonRows(),
   });
 
+  await channel.send({
+    content: '@everyone',
+    allowedMentions: { parse: ['everyone'] },
+  });
+
   await interaction.reply({
     embeds: [
-      buildErrorEmbed('Alerts panel posted', `Sent the analyst alert panel to <#${ALERTS_CHANNEL_ID}>.`).setColor(0x2563eb),
+      buildErrorEmbed('Alerts panel posted', `Sent the analyst alert panel and @everyone ping to <#${ALERTS_CHANNEL_ID}>.`).setColor(0x2563eb),
     ],
     flags: MessageFlags.Ephemeral,
   });