The official VLDC telegram group bot.
- 😼 core – core
- 😼 version – show this message
- 😻 still – do u remember it?
- 😾 uwu – don't uwu!
- 🤭 mute – mute user for N minutes
- 🔫 roll – life is so cruel... isn't it?
- ⚔️ banme – commit sudoku
- 🔪 ban – ban! ban! ban!
- 🎄 tree – advent of code time!
- ⛔🤬 coc – VLDC/GDG VL Code of Conduct
- 🛠 more than 70k? – try to hire!
- 💻 got sk1lzz? – put them to use!
- 👁 smell like PRISM? nononono!
- 💰 kozula Don't argue with kozula rate!
- 😼 smile mode – allow only stickers in the chat
- 🛠 since mode – under construction
- 🧼 towel mode – anti bot
- 🙃 fools mode – what? not again!
- 🦠 covid mode – fun and gamez
- 🤫 nastya mode – stop. just stop
Setup your env vars in example.env and rename it to .env. Don't push .env to public repos!
make up
make build
Create test Telegram bot, and store TOKEN and chat id, you will need it for developing.
User make to up dev services:
Usage: make [task]
task help
------ ----
build Build all
up Up All and show logs
update Restart bot after files changing
stop Stop all
down Down all
test Run tests
lint Run linters (black, flake8, mypy, pylint)
format Format code (black)
help Show help messageDon't forget run make lint and make test before commit! For code formatting we are use black, so, just run make format to fire it :3
Create launch.json under your .vscode directory in project, add the following content onto it:
{
"version": "0.2.0",
"configurations": [
{
"name": "Docker Python",
"type": "python",
"request": "attach",
"port": 5678,
"host": "localhost",
"pathMappings": [
{
"localRoot": "${workspaceFolder}",
"remoteRoot": "/app"
}
],
}
]
}
Also, put DEBUGGER=True into your .env file. After that you can do debugging with VS Code, by running containerized application and hitting Run -> Start Debugging or F5 button.
Bug reports, bug fixes and new features are always welcome. Please open issues and submit pull requests for any new code.