docs: add README, MIT LICENSE, and SVG logo#1
Conversation
mocasus
commented
May 21, 2026
- README dengan logo banner, badges, quick-start lengkap
- Panduan dapetin token Telegram (BotFather) & Discord (Developer Portal)
- Cara setup webhook public (ngrok / Cloudflare tunnel)
- Struktur project, tabel command, roadmap, contribution guide
- LICENSE MIT untuk open source
- README dengan logo banner, badges, quick-start lengkap - Panduan dapetin token Telegram (BotFather) & Discord (Developer Portal) - Cara setup webhook public (ngrok / Cloudflare tunnel) - Struktur project, tabel command, roadmap, contribution guide - LICENSE MIT untuk open source
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: fd5d94f76e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| 2. **Build**: | ||
| ```bash | ||
| npm run build | ||
| npm run db:migrate deploy |
There was a problem hiding this comment.
Run Prisma deploy subcommand in production step
The production instructions currently use npm run db:migrate deploy, but db:migrate is defined as prisma migrate dev in package.json, so this expands to prisma migrate dev deploy instead of prisma migrate deploy. In a real deploy pipeline, that invokes the development workflow (interactive/shadow DB behavior) rather than applying committed migrations, which can block or mis-handle production rollout when users follow this README verbatim.
Useful? React with 👍 / 👎.