Add MineGeo gameplay systems and interface
This commit is contained in:
@@ -1,5 +1,23 @@
|
||||
# Deploy MineGeo
|
||||
|
||||
Optional Discord map and multiplayer-party announcements use `DISCORD_BOT_TOKEN`,
|
||||
`DISCORD_MAPS_CHANNEL_ID`, and `DISCORD_PARTIES_CHANNEL_ID`. All published parties
|
||||
use the same configured channel. Follow [Discord bot setup](discord-integration.md)
|
||||
for creation, permissions, Vercel variables, and retries. Apply the Discord queue
|
||||
migration before deploying this feature; the bot token stays server-only.
|
||||
|
||||
Optional community buttons appear in the footer when `MINEGEO_DISCORD_URL` or
|
||||
`MINEGEO_TELEGRAM_URL` is configured. Set these public links in `.env.local` for
|
||||
local development (ordinary `.env` also works). Restart the local server after
|
||||
changing a link. For the hosted site, add the same names as Production Config
|
||||
variables in the MineGeo Vercel project, then redeploy. These values are public
|
||||
destinations; no Discord bot token or Telegram API key is needed.
|
||||
|
||||
Discord accepts HTTPS links on `discord.gg`, `discord.com`, `www.discord.com`,
|
||||
and `discordapp.com`. Telegram accepts `t.me` and `telegram.me`, including group
|
||||
invite links. Blank, malformed, or unsupported URLs hide the corresponding
|
||||
button. Each button opens its configured destination in a new tab.
|
||||
|
||||
Run `npm run deploy` from the project directory. The script collects all web
|
||||
source files and public assets, uploads them in one request, waits for the build,
|
||||
and prints the deployment URL. It uses the [Vercel deployments API](https://vercel.com/docs/rest-api/deployments/create-a-new-deployment). The database credentials already configured in
|
||||
|
||||
Reference in New Issue
Block a user