4.CloneBot V2 don't use your bandwidth or Internet connection while cloning data but it can if hosted on your local machine or VPS for calling required Telegram APIs to update the progress or to generate required response.
5.This Project comes with GNU License, please consider reading it before using this.
6.Name of zip file should be only accounts.zip and it should only contain .json files not folders!
7.Use your own Docker Image for deploying on VPS or local machine! using your own Docker Image for deploying on platforms like Heroku, Okteto or Scalingo will cause Account to be suspended. In that case use Repository's official Docker Image.
CloneBot V2 is very straight forward and easy to use bot. If you deployed your CloneBot V2 then consider adding commands in it through @BotFather to make it easy for other users to know bot commands, here is the commands list to be set in @BotFather:
-accounts.zip then send it to bot and write /sa in caption or send /sa as reply to accounts.zip file. Don't have Service Accounts? Learn here how to createaccounts.zip then send it to bot and write /sa in caption or send /sa as reply to accounts.zip file. Don't have Service Accounts? Learn here how to create/folders to your CloneBot V2 and then bot will show Shared Drives name in which you added your Service Accounts's Google Group, select Shared Drive or directory available in it as destination. Not added Service Accounts in Google Group? Learn here how to do./ban and /unban command is to unauthorize or authorize user again and /id command is to get your Telegram User ID.
⛔NOTE: Shared Drive is a temporary storage! use it carefully and keep backup of your data always with you.
Generally, I seen people, blindly running and ignoring options provided by Setup for installing Python and PIP which is most important thing to make Service Accounts or to run CloneBot V2. People like it are just there to flood out support chat and abuse moderators too! Hence I made this Section to tackle this special disease. Lets name this disease Setup-Blindness😂
+Generally, I seen people, blindly running and ignoring options provided by Setup for installing Python and PIP which is most important thing to make Service Accounts or to run CloneBot V2. People like it are just there to flood out support chat and abuse moderators too! Hence I made this Section to tackle this special disease. Lets name this disease Setup-Blindness😂
Customize Installation:
Next.'python' is not recognized as an internal or external command,
operable program or batch file.
'py3' is not recognized as an internal or external command,
+operable program or batch file.
'py' is not recognized as an internal or external command,
operable program or batch file.
⛔NOTE: 1.Docker Image only accepts 2.Use your own Docker Image for deploying on VPS only! Using it for deploying platforms like Heroku will simply cause Account suspension. 2.Use your own Docker Image for deploying on VPS only! Using it for deploying ON platforms like Heroku, Okteto or Scalingo will simply cause Account suspension. Heroku is very famous PaaS (Platform as a Service) platform and it provides very simple user environment as well as you can deploy CloneBot V2 very quickly on Heroku to run it continuously for 24 Hours.'pip3' is not recognized as an internal or external command,
@@ -133,7 +136,7 @@ https://gist.githubusercontent.com/UserName/0ee24eXXXXXXXXXXXXXXX6b/raw/config.i
3.Want to build own docker image? alright! here is the guide.
CONFIG_FILE_URL⚡Deploy on Heroku
Config.ini file
- ->Open config.ini file in any text editor and enter the values of variables as written here
-
Or you can download your config.ini file from external source using CONFIG_FILE_URL by using Command-line:
+ ->Open Config.ini file in any text editor and enter the values of variables as written here
+
Or you can download your Config.ini file from external source using CONFIG_FILE_URL by using Command-line:
->curl CONFIG_FILE_URL >> telegram_gcloner/config.ini
CloneBot V2 is also deployable to Scalingo cloud, Just deploy Scalingo Branch.
Switch to Scalingo Branch for guide.
-Service Accounts are just like normal Google Account and thus have same Upload or Download limits as Google Account which is 750GB Upload and 10TB Download. They are used to act on behalf of a Google Account and hence we can use them to prevent hitting Google Drive limits by creating them in a bulk amount. After creating Service Accounts, we have to add them in Google Group so that we can directly add Google Group's Email ID in Shared Drive at place of adding each Service Accounts manually.