Telegram Drive
Find a file
2023-08-16 22:40:41 +05:30
.github Update build.yml 2023-08-16 21:59:58 +05:30
.vscode update 2023-08-16 03:24:51 +05:30
cache initial commit 2023-08-07 01:02:46 +05:30
database update 2023-08-16 20:57:03 +05:30
models update 2023-08-16 22:40:41 +05:30
public chnaged package name 2023-08-16 03:23:02 +05:30
routes chnaged package name 2023-08-16 03:23:02 +05:30
schemas chnaged package name 2023-08-16 03:23:02 +05:30
services update 2023-08-16 22:40:41 +05:30
types websocket login 2023-08-15 01:06:24 +05:30
utils changed migrations and added nginx 2023-08-16 18:18:32 +05:30
.gitignore added official tg client info 2023-08-16 02:32:08 +05:30
docker-compose.yml fix compose errors 2023-08-16 20:57:00 +05:30
Dockerfile update 2023-08-16 04:03:28 +05:30
go.mod changed migrations and added nginx 2023-08-16 18:18:32 +05:30
go.sum changed migrations and added nginx 2023-08-16 18:18:32 +05:30
LICENSE Create LICENSE 2023-08-16 18:50:35 +05:30
main.go changed migrations and added nginx 2023-08-16 18:18:32 +05:30
nginx.conf nginx remove upload limit 2023-08-16 22:23:01 +05:30
nginx_nossl.conf nginx remove upload limit 2023-08-16 22:23:01 +05:30
README.md update readme 2023-08-16 18:45:53 +05:30

Telegram Drive

Table of Contents
  1. How to make your own
  2. Setting up things

Demo

demo

UI Repo

Deploy using docker-compose

First clone the repository

git clone https://github.com/divyam234/teldrive
cd teldrive

now create the .env file with your variables. and start your container: If you are deploying without https replace nginx.conf with nginx_nossl.conf in docker-compose.yml.It should look like this.Replace #DBURL with POSTGRES URL to RUN first time migrations

volumes:
      - ./nginx_nossl.conf:/etc/nginx/conf.d/default.conf
ports:
    - 8000:8000
docker compose up -d

Setting up things

If you're locally hosting, create a file named .env in the root directory and add all the variables there. An example of .env file:

API_ID=1234
API_HASH=abc
CHANNEL_ID=1234
JWT_SECRET=abc
DATABASE_URL=abc
MULTI_CLIENT=true # true or false here
MULTI_TOKEN1=55838383:yourfirstmulticlientbottokenhere
MULTI_TOKEN2=55838383:yoursecondmulticlientbottokenhere
MULTI_TOKEN3=55838383:yourthirdmulticlientbottokenhere

Mandatory Vars

Before running the bot, you will need to set up the following mandatory variables:

  • API_ID : This is the API ID for your Telegram account, which can be obtained from my.telegram.org.

  • API_HASH : This is the API hash for your Telegram account, which can also be obtained from my.telegram.org.

  • JWT_SECRET : Used for signing jwt tokens

  • DATABASE_URL : Connection String obtained from Postgres DB (you can use Neon db as free alternative fro postgres)

  • CHANNEL_ID : This is the channel ID for the log channel where the bot will forward media messages and store these files to make the generated direct links work. To obtain a channel ID, create a new telegram channel (public or private), post something in the channel, forward the message to @missrose_bot and reply the forwarded message with the /id command. Copy the forwarded channel ID and paste it into the this field.

Optional Vars

In addition to the mandatory variables, you can also set the following optional variables:

  • MULTI_CLIENT : Enable or Disable Multi Token mode. If true you have pass atleast one Multi Token
  • MULTI_TOKEN[1....] : Recommended to add atleast 10-12 tokens

For making use of Multi-Client support

Note

What it multi-client feature and what it does?
This feature shares the Telegram API requests between other bots to avoid getting floodwaited (A kind of rate limiting that Telegram does in the backend to avoid flooding their servers) and to make the server handle more requests.

To enable multi-client, generate new bot tokens and add it as your environmental variables with the following key names.

MULTI_TOKEN1: Add your first bot token here.

MULTI_TOKEN2: Add your second bot token here.

you may also add as many as bots you want. (max limit is not tested yet) MULTI_TOKEN3, MULTI_TOKEN4, etc.

Warning

Don't forget to add all these bots to the CHANNEL_ID as admin for the proper functioning

FAQ

  • How to get Postgres DB url ?

You spin up local postgres instance but its not recommended as there is lot of hassle in backup and transfering data.Recommended way is to use any free cloud postgres DB.I will recommend to use Neon DB.

Contributing

Feel free to contribute to this project if you have any further ideas.