refactor!: rebrand miti99bot to tiennm99bot

BREAKING CHANGE: the Go module path is now github.com/tiennm99/tiennm99bot,
the default sticker pack is stickers_by_<bot username>, and the health body,
deploy DM, User-Agents and image names say tiennm99bot.
This commit is contained in:
tiennm99 committed 2026-10-07 15:14:02 +07:00
1 parent 79104ef3d7
commit 7008a57cf5
160 files changed
+388 -387

No files matched your search

+3 -3
View File
@@ -1,6 +1,6 @@
# renderer
Part of miti99bot: the service behind `/wheelofnames`, `/gacha`, and
Part of tiennm99bot: the service behind `/wheelofnames`, `/gacha`, and
`/genshin`, deployed by the root `compose.yml` as the `renderer` service.
Self-hosted API that renders wheel-of-names GIF animations and Genshin-style
meteor wish MP4 animations with Remotion, and card-pack gacha wish MP4
@@ -177,8 +177,8 @@ Use a container runtime first. Static-only platforms cannot satisfy
dependencies, and FFmpeg/compositor support.
```sh
docker build -t miti99bot-renderer .
docker run --rm -p 3000:3000 miti99bot-renderer
docker build -t tiennm99bot-renderer .
docker run --rm -p 3000:3000 tiennm99bot-renderer
```
Recommended starting resources: 1-2 vCPU and 1-2 GB RAM, with
+1 -1
View File
@@ -1,6 +1,6 @@
# Deployment
## miti99bot compose
## tiennm99bot compose
The root `compose.yml` builds this folder as the `renderer` service and points
the bot at it over the compose network. The API has no authentication: it is
@@ -1,6 +1,6 @@
# miti99bot Integration
# tiennm99bot Integration
miti99bot's `/wheelofnames` renders its wheel with this service, configured
tiennm99bot's `/wheelofnames` renders its wheel with this service, configured
by `RENDERER_URL`, the service's base URL. The service is internal to
the compose network, so requests carry no credentials. Winner handling stays
explicit:
@@ -42,7 +42,7 @@ winner selection is used.
## Gacha
`/gacha` in miti99bot calls `POST /api/gacha` on the same service.
`/gacha` in tiennm99bot calls `POST /api/gacha` on the same service.
The bot appends the route to `RENDERER_URL`, picks the result and rarity
itself, and sends the MP4 with `sendAnimation`. On any failure it falls back to
a text reply.
+2 -2
View File
@@ -1,11 +1,11 @@
{
"name": "miti99bot-renderer",
"name": "tiennm99bot-renderer",
"version": "0.1.0",
"lockfileVersion": 3,
"requires": true,
"packages": {
"": {
"name": "miti99bot-renderer",
"name": "tiennm99bot-renderer",
"version": "0.1.0",
"dependencies": {
"@remotion/bundler": "4.0.485",
+1 -1
View File
@@ -1,5 +1,5 @@
{
"name": "miti99bot-renderer",
"name": "tiennm99bot-renderer",
"version": "0.1.0",
"private": true,
"type": "module",
+1 -1
View File
@@ -278,7 +278,7 @@ const renderBack = () => {
const print = el('div', 'recap-card-print');
const seal = el('span', 'recap-print-seal wish-moon-seal');
seal.append(el('span', '', moon));
print.append(el('span', 'recap-print-channel'), seal, el('span', 'recap-print-edition', 'miti99bot'));
print.append(el('span', 'recap-print-channel'), seal, el('span', 'recap-print-edition', 'tiennm99bot'));
return print;
};