1
0
forked from sass/tipibot
Files
tipibot/docs/LAN_FIENTA_SETUP.md
2026-04-29 22:38:47 +03:00

2.0 KiB

LAN Fienta Setup

This profile runs the same codebase as a separate Discord bot process:

$env:BOT_PROFILE="lan"
python bot.py

Environment

Required .env values:

BOT_PROFILE=lan
DISCORD_BOT_LAN=...
GUILD_ID_LAN=1301145356750426192
SHEET_ID_LAN=1cYEI2EmQDMZdVOarbOkVw7IHsnfqtYbWhA-6zC_r-zw
PB_ECONOMY_COLLECTION_LAN=economy_users_lan
PB_FIENTA_COLLECTION_LAN=fienta_registrations_lan
FIENTA_WEBHOOK_SECRET=<optional-long-random-secret>
FIENTA_WEBHOOK_PORT=8090
FIENTA_ADMIN_ALERT_CHANNEL_ID=1478302279894302812

The LAN bot must be invited to the LAN server and to the dev server that owns the alert channel.

Fienta Webhooks

Use these URLs in Fienta:

Ostu sooritamisel:
https://veebikonks.tipilan.ee/fienta/purchase

Registreerimisvormi täitmisel peale ostu:
https://veebikonks.tipilan.ee/fienta/registration

Leave Pileti valideerimisel empty for now.

The old secret-token endpoint is still supported for testing:

https://veebikonks.tipilan.ee/fienta/webhook/<FIENTA_WEBHOOK_SECRET>

Caddy

If Caddy is on the same Docker network as the bot service:

veebikonks.tipilan.ee {
    reverse_proxy /fienta/* bot:8090
}

If Caddy runs on the host, make sure localhost:8090 points to the bot webhook, not PocketBase. The current compose file publishes PocketBase on host port 8090, so host-level Caddy cannot also proxy that same host port to the bot unless PocketBase is moved or the bot is exposed through a different host route.

Ticket Mapping

  • 595507 - CS2 participant, public sheet row, CS2/team/language roles
  • 595509 - CS2 reserve, roles only
  • 595510 - CS2 manager, CS2/team/language/Manager roles
  • 595912 - LoL participant, public sheet row, LoL/team/language roles

Public sheet rows:

  • CS2: rows 6 through 37
  • LoL: rows 6 through 17

Admin Command

Use /fientasync in the LAN server to re-apply stored Fienta registrations to Discord roles and the public sheet.