The url where the app will be hosted i.e for heroku it will be https://{appname}.herokuapp.com or for self-hosted server it will be https://{hostname_or_ip}:{port} where port is usally 8443

To create a Google Cloud project:

1. Open the Google Cloud Console.
2. At the top-left, click Menu > IAM & Admin > Create a Project.
3. In the Project Name field, enter a descriptive name for your project.
   Optional: To edit the Project ID, click Edit. The project ID can't be changed after the project is created, so choose an ID that meets your needs for the lifetime of the project.
   In the Location field, click Browse to display potential locations for your project. Then, click Select
4. Click Create. The console navigates to the Dashboard page and your project is created within a few minutes.

Configure the Project:

1. Open the Google Cloud Console Dashboard and select your project
2. At the top-left, click Menu > APIs & Services
3. On the left side menu,Select Library/
4. Search for Google Drive in the search bar the API library and Select and Enable Google Drive API
5. Again at the top-left, click Menu > APIs & Services
6. On the left side menu,Select Credentials, select Create credentials, then OAuth client ID.
7. You may be prompted to set a product name on the Consent screen; if so, click Configure consent screen, supply the requested information following the notes below, and click Save to return to the Credentials screen

OAuth consent screen Configuration:

1. Select user type as external
2. Fill the required details
3. In the scopes page,Click on Add or Remove Scopes
4. Search and Add /auth/drive and /auth/drive.metadata scopes and click on update
5. You should see the scopes added in Your Sensitive Scopes Section
6. Click on Save and Continue for rest of the sections
7. On the OAuth consent screen Click on Publish App and Confirm
8. Ignore Needs verification warning for the time being,the users will only see the warning while authorizing but please note there's a limit to number of users for unverified apps
8. Again On the left side menu,select Credentials and then select Create credentials, then OAuth client ID
9. Select Web Application for the Application Type. Follow the instructions to enter JavaScript origins, redirect URIs, or both.
   1. In Javascript Origins add your domain name which should be APP_URL
   2. In Authorized redirect URIs Add your redirect uri which should be APP_URL/oauth_handler
10. Click Create.
11. Download your client_secret.json from the popup modal or from under OAuth 2.0 Client IDs
12. Open client_secret.json and copy the whole config as CLIENT_CONFIG

The bot token for telegram bot, for more info on how to create a bot and get a token visit How to create a telegram bot

A random alphanumeric text used as a salt in generating state for oauth authorization.
Not required in heroku caused generator is used while deploying

The telegram bot url,this is usually in the form https://t.me/{bot_username}

Should there be a filter where password is required for access to the bot
Set as "True" or "False"

Password used for allowing a group chat access to the bot,should be set if "ALLOWLIST" is enabled

Password used for allowing a user access to the bot,should be set if "ALLOWLIST" is enabled

The application hosted in heroku free dyno sleeps after 20 minutes of no activity,to conteract this the application can ping itself every 5 minutes and keep itself alive.
Should be set to either "True" or "False"

Heroku dynos are restarted every 24 hours + random(0-216)minutes,but if there is a restart before that the restart time is reset. The bot can give you the approx restart time and restart itself when no activity occurs for 4 hours if it has the Platform API Token
The token can be found here

The DATABASE URI for custom SQL Database

The URL for connecting to custom redis instance

The log level to be displayed in console,all the log levels can be found here
Only numeric value is supported

Custom port for hosting the application,but only Ports supported by telegram should be used when the application is not hosted behind a reverse proxy