Fill up rest of the fields. Meaning of each fields are discussed below:
BOT_TOKEN : The telegram bot token that you get from @BotFather
GDRIVE_FOLDER_ID : This is the folder ID of the Google Drive Folder to which you want to upload all the mirrors.
DOWNLOAD_DIR : The path to the local folder where the downloads should be downloaded to
DOWNLOAD_STATUS_UPDATE_INTERVAL : A short interval of time in seconds after which the Mirror progress message is updated. (I recommend to keep it 5 seconds at least)
OWNER_ID : The Telegram user ID (not username) of the owner of the bot
AUTO_DELETE_MESSAGE_DURATION : Interval of time (in seconds), after which the bot deletes it's message (and command message) which is expected to be viewed instantly. Note: Set to -1 to never automatically delete messages
IS_TEAM_DRIVE : (Optional field) Set to "True" if GDRIVE_FOLDER_ID is from a Team Drive else False or Leave it empty.
Heroku-Note: Doing authorizations ( /authorize command ) through telegram wont be permanent as heroku uses ephemeral filesystem. They will be reset on each dyno boot. As a workaround you can:
Make a file authorized_chats.txt and write the user names and chat_id of you want to authorize, each separated by new line
Then force add authorized_chats.txt to git and push it to heroku