Backend code of https://rtapp-verify-backend.recaptime.autocode.gg as deployed to Autocode through GitLab CI.
Andrei Jiroh Halili 0909e2fd10 | ||
---|---|---|
.gitlab/ci | ||
.vscode | ||
functions | ||
lib | ||
readme | ||
tests/cases | ||
www | ||
.gitignore | ||
.gitpod.Dockerfile | ||
.gitpod.yml | ||
.trigger-build | ||
LICENSE | ||
README.md | ||
package-lock.json | ||
package.json | ||
payloads.json | ||
stdlib.json |
README.md
Verification Endpoint API backend
This is our source code for the Verification Endpoint API handler and Discord bot running on Autocode, usually synchorized every hour through GitLab CI.
API calls from verify.rtapp.<tk|io>
domain will be trnsparently redirected to the production release at rtapp-verify-backend.recaptime.autocode.gg
.
Development
Requires Node.js 14+ and Autocode CLI if you want to do local development or even deployment to development/production environments on Autocode.
Setup
npm install
npm start
to run an local FunctionScript gateway with hot reload included.curl -i http://localhost:8170/recaptime/rtapp-verify-backend/ping
Getting help
- Discord: For Autocode users who are in the official Autocode Discord sevrer or Miraheze users on Miraheze Discord, just ping Andrei Jiroh (
Andrei Jiroh#7159
). You can also optionally join Recap Time Squad's Discord server and ask for help under#rtapp-verify-bot
channel. - Issue tracker: We track issues on https://gitlab.com/RecapTime/verify/issues instead.
Related Projects
- Main project repo (GitHub mirror is available through we use issue forms) - all the verification metadata are being stored publicly, through some private data are held in an MongoDB database instead.
Credits
- Hakiki for the landing page guide: https://hakiki.api.stdlib.com/blog@dev/landingpage.html