Heroku Deployable Method:

• I have collected some cool features from various repositories and merged them in one.
• So, credits goes to original repo holder, not to me. I have just collected them.
• This (or any custom) repo is not supported in official bot support group.
• So if you have any issue then check first that issue is in official repo or not, You are only allowed to report that issue in bot support group if that issue is also present in official repo.

1. Added Inline Buttons
2. Added /del command to delete files from drive
3. /list module will post search result on telegra.ph

1. unzipmirror
2. Update tracker list dynamically
3. Fix SSL handsake error

What is this repo about?

This is a telegram bot writen in python for mirroring files on the internet to our beloved Google Drive.

Inspiration

This project is heavily inspired from @out386 's telegram bot which is written in JS.

Features supported:

• Mirroring direct download links to google drive
• Mirroring Mega.nz links to google drive (In development stage)
• Mirror Telegram files to google drive
• Mirror all youtube-dl supported links
• Extract these filetypes and uploads to google drive

ZIP, RAR, TAR, 7z, ISO, WIM, CAB, GZIP, BZIP2, APM, ARJ, CHM, CPIO, CramFS, DEB, DMG, FAT, HFS, LZH, LZMA, LZMA2, MBR, MSI, MSLZ, NSIS, NTFS, RPM, SquashFS, UDF, VHD, XAR, Z.

• Copy files from someone's drive to your drive (using Autorclone)
• Service account support in cloning and uploading
• Download progress
• Upload progress
• Download/upload speeds and ETAs
• Docker support
• Uploading To Team Drives.
• Index Link support
• Shortener support

Bot commands to be set in botfather

mir - Start Mirroring
tarmir - Upload tar (zipped) file
unzip - Extract files
clone - copy folder to drive
yt - mirror YT-DL support link
taryt - mirror youtube playlist link as tar
cancel - Cancel a task
cancelall - Cancel all tasks
del - Delete file from Drive
list - [query] searches files in G-Drive
status - Get Mirror Status message
stats - Bot Usage Stats
help - Get Detailed Help
log - Bot Log [owner only]

How to deploy?

Deploying is pretty much straight forward and is divided into several steps as follows:

Installing requirements

- Install requirements
For Debian based distros

sudo apt install python3 sudo snap install docker

- For Arch and it's derivatives:

sudo pacman -S docker python

## Setting up config file

cp config_sample.env config.env

- Remove the first line saying:

REMOVE_THIS_LINE=True

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.
- **TELEGRAPH_TOKEN** : Telegraph token by clicking here [clicking here](https://telegraph-token.sonywegas.repl.run/) or generated by running :

python3 generate_telegraph_token.py

- **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.
- **USE_SERVICE_ACCOUNTS**: (Optional field) (Leave empty if unsure) Whether to use service accounts or not. For this to work see  "Using service accounts" section below.
- **INDEX_URL** : (Optional field) Refer to https://github.com/maple3142/GDIndex/ The URL should not have any trailing '/'
- **API_KEY** : This is to authenticate to your telegram account for downloading Telegram files. You can get this from https://my.telegram.org DO NOT put this in quotes.
- **API_HASH** : This is to authenticate to your telegram account for downloading Telegram files. You can get this from https://my.telegram.org
- **USER_SESSION_STRING** : Generate String session by [clicking here](https://string-session.sonywegas.repl.run/) **OR** you can generate by running :

python3 generate_string_session.py

- **MEGA_API_KEY**: Mega.nz api key to mirror mega.nz links. Get it from [Mega SDK Page](https://mega.nz/sdk)
- **MEGA_EMAIL_ID**: Your email id you used to sign up on mega.nz for using premium accounts (Leave th)
- **MEGA_PASSWORD**: Your password for your mega.nz account 
- **STOP_DUPLICATE_MIRROR**: (Optional field) (Leave empty if unsure) if this field is set to `True` , bot will check file in drive, if it is present in drive, downloading will ne stopped. (Note - File will be checked using filename, not using filehash, so this feature is not perfect yet)
- **BLOCK_MEGA_LINKS**: (Optional field) If you want to remove mega.nz mirror support (bcoz it's too much buggy and unstable), set it to `True`.
- **SHORTENER**: (Optional field) if you want to use shortener in Gdrive and index link, fill shotener url here. Examples :-

> exe.io

> gplinks.in

> shrinkme.io

> urlshortx.com

> shortzon.com

Note :- Above are the supported url shorteners. Except these only some url shorteners are supported. If you want to use any other url shortener then first ask me that shortener is supported or not.
- **SHORTENER_API**: Fill your shortener api key if you are using shortener.

Note: You can limit maximum concurrent downloads by changing the value of MAX_CONCURRENT_DOWNLOADS in aria.sh. By default, it's set to 4
 
## Getting Google OAuth API credential file

- Visit the [Google Cloud Console](https://console.developers.google.com/apis/credentials)
- Go to the OAuth Consent tab, fill it, and save.
- Go to the Credentials tab and click Create Credentials -> OAuth Client ID
- Choose Desktop and Create.
- Use the download button to download your credentials.
- Move that file to the root of mirror-bot, and rename it to credentials.json
- Visit [Google API page](https://console.developers.google.com/apis/library)
- Search for Drive and enable it if it is disabled
- Finally, run the script to generate token file (token.pickle) for Google Drive:

pip install google-api-python-client google-auth-httplib2 google-auth-oauthlib python3 generate_drive_token.py

- Run the script to generate token file(token.pickle) for Google Drive:

python3 generate_drive_token.py

## Deploying

- Start docker daemon (skip if already running):

sudo dockerd

- Build Docker image:

sudo docker build . -t drive-bot-ultimate

- Run the image:

sudo docker run drive-bot-ultimate

## Deploying on Heroku

- Install [Heroku cli](https://devcenter.heroku.com/articles/heroku-cli)
- Login into your heroku account with command:

heroku login

- Create a new heroku app:

heroku create appname

- Select This App in your Heroku-cli: 

heroku git:remote -a appname

- Change Dyno Stack to a Docker Container:

heroku stack:set container

- Add Heroku Postgres (only if you are deploying it for the 1st time)

heroku addons:create heroku-postgresql

- Add Private Credentials and Config Stuff:

git add -f credentials.json token.pickle config.env heroku.yml

- Commit new changes:

git commit -m "Added Creds."

- Push Code to Heroku:

git push heroku master --force

- Restart Worker by these commands:

heroku ps:scale worker=0

heroku ps:scale worker=1

# Using service accounts for uploading to avoid user rate limit
For Service Account to work, you must set USE_SERVICE_ACCOUNTS="True" in config file or environment variables
Many thanks to [AutoRClone](https://github.com/xyou365/AutoRclone) for the scripts
**NOTE:** Using service accounts is only recommended while uploading to a team drive.
## Generating service accounts
Step 1. Generate service accounts [What is service account](https://cloud.google.com/iam/docs/service-accounts)
---------------------------------
Let us create only the service accounts that we need. 
**Warning:** abuse of this feature is not the aim of this project and we do **NOT** recommend that you make a lot of projects, just one project and 100 sa allow you plenty of use, its also possible that over abuse might get your projects banned by google. 

Note: 1 service account can copy around 750gb a day, 1 project can make 100 service accounts so that's 75tb a day, for most users this should easily suffice.

`python3 gen_sa_accounts.py --quick-setup 1 --new-only`

A folder named accounts will be created which will contain keys for the service accounts

NOTE: If you have created SAs in past from this script, you can also just re download the keys by running:

python3 gen_sa_accounts.py --download-keys project_id

### Add all the service accounts to the Team Drive
- Run:

python3 add_to_team_drive.py -d SharedTeamDriveSrcID

# Youtube-dl authentication using .netrc file
For using your premium accounts in youtube-dl, edit the netrc file (in the root directory of this repository) according to following format:

machine host login username password my_youtube_password

where host is the name of extractor (eg. youtube, twitch). Multiple accounts of different hosts can be added each separated by a new line