You can also Find me on Telegram
Simplest method is to Deploy Me in heroku🤗.
The bot is based on the original work done by PaulSonOfLars This repo was just revamped to suit an Anime-centric community. All original credits go to Paul and his dedication, Without his efforts, this fork would not have been possible!
There are two possible ways of configuring your bot: a config.py file, or ENV variables.
The prefered version is to use a config.py
file, as it makes it easier to see all your settings grouped together.
This file should be placed in your tg_bot
folder, alongside the __main__.py
file .
This is where your bot token will be loaded from, as well as your database URI (if you're using a database), and most of
your other settings.
It is recommended to import sample_config and extend the Config class, as this will ensure your config contains all defaults set in the sample_config, hence making it easier to upgrade.
An example config.py
file could be:
from tg_bot.sample_config import Config
class Development(Config):
OWNER_ID = 736706850 # my telegram ID
OWNER_USERNAME = "Charlie_jin" # my telegram username
CASH_API_KEY = None # Get one from https://www.alphavantage.co/support/#api-key
TIME_API_KEY = None # Get one from https://timezonedb.com/register
API_OPENWEATHER = False #Get API_OPENWEATHER FROM OFFICAL SITE https://da.gd/VAW3
AI_API_KEY = None # Coffeehouse chatbot api key, get one from https://coffeehouse.intellivoid.info/
API_KEY = "your bot api key" # my api key, as provided by the botfather
SQLALCHEMY_DATABASE_URI = 'postgresql://username:password@localhost:5432/database' # sample db credentials
MESSAGE_DUMP = '-1234567890' # some group chat that your bot is a member of
USE_MESSAGE_DUMP = True
SUDO_USERS = [736706850 1199252608] # List of id's for users which have sudo access to the bot.
LOAD = []
NO_LOAD = ['translation']
If you can't have a config.py file (EG on heroku), it is also possible to use environment variables. The following env variables are supported:
-
ENV
: Setting this to ANYTHING will enable env variables -
CASH_API_KEY
:Get one from https://www.alphavantage.co/support/#api-key -
TIME_API_KEY
:Get one from https://timezonedb.com/register -
API_OPENWEATHER
:Get API_OPENWEATHER FROM OFFICAL SITE https://da.gd/VAW3 -
AI_API_KEY
:Coffeehouse chatbot api key, get one from https://coffeehouse.intellivoid.info/ -
WALL_API
:Get one from https://wall.alphacoders.com/api.php -
TOKEN
: Your bot token, as a string. -
OWNER_ID
: An integer of consisting of your owner ID -
OWNER_USERNAME
: Your username -
DATABASE_URL
: Your database URL -
MESSAGE_DUMP
: optional: a chat where your replied saved messages are stored, to stop people deleting their old -
LOAD
: Space separated list of modules you would like to load -
NO_LOAD
: Space separated list of modules you would like NOT to load -
WEBHOOK
: Setting this to ANYTHING will enable webhooks when in env mode messages -
URL
: The URL your webhook should connect to (only needed for webhook mode) -
SUDO_USERS
: A space separated list of user_ids which should be considered sudo users -
SUPPORT_USERS
: A space separated list of user_ids which should be considered support users (can gban/ungban, nothing else) -
WHITELIST_USERS
: A space separated list of user_ids which should be considered whitelisted - they can't be banned. -
CERT_PATH
: Path to your webhook certificate -
PORT
: Port to use for your webhooks -
DEL_CMDS
: Whether to delete commands from users which don't have rights to use that command -
STRICT_GBAN
: Enforce gbans across new groups as well as old groups. When a gbanned user talks, he will be banned. -
WORKERS
: Number of threads to use. 8 is the recommended (and default) amount, but your experience may vary. Note that going crazy with more threads wont necessarily speed up your bot, given the large amount of sql data accesses, and the way python asynchronous calls work. -
BAN_STICKER
: Which sticker to use when banning people. -
ALLOW_EXCL
: Whether to allow using exclamation marks ! for commands as well as /.
If you wish to use a database-dependent module (eg: locks, notes, userinfo, users, filters, welcomes), you'll need to have a database installed on your system. I use postgres, so I recommend using it for optimal compatibility.
In the case of postgres, this is how you would set up a the database on a debian/ubuntu system. Other distributions may vary.
- install postgresql:
sudo apt-get update && sudo apt-get install postgresql
- change to the postgres user:
sudo su - postgres
- create a new database user (change YOUR_USER appropriately):
createuser -P -s -e YOUR_USER
This will be followed by you needing to input your password.
- create a new database table:
createdb -O YOUR_USER YOUR_DB_NAME
Change YOUR_USER and YOUR_DB_NAME appropriately.
- finally:
psql YOUR_DB_NAME -h YOUR_HOST YOUR_USER
This will allow you to connect to your database via your terminal. By default, YOUR_HOST should be 0.0.0.0:5432.
You should now be able to build your database URI. This will be:
sqldbtype://username:pw@hostname:port/db_name
Replace sqldbtype with whichever db youre using (eg postgres, mysql, sqllite, etc) repeat for your username, password, hostname (localhost?), port (5432?), and db name.
Credits - Charlie Jin