python-telegram-bot VS git

I've developed it using python 3.9 and the library python-telegram-bot which is really awesome. The bot receives updates and messages directly from the Telegram webhook, much better and faster than the hold "polling" method!

it's based on the Python Telegram Bot framework (they call it a wrapper but if you include the extensions it's basically a framework).

I had never heard of that wrapper, but twhile that one seems to be an implementation from the ground up using async and await, the wrapper i made is based on the official python wrapper from telegram and uses a more object oriented approach to ease the developement of bots.

I understand the whole part of writing the code, but how does the actual deployment of an app work? I have been playing around to better understand it, trying to deploy the python telegram bot on my webhosting. https://github.com/python-telegram-bot/python-telegram-bot

To communicate with Telegram bot-API I use the python-telegram-bot library. It processes each message or other type of communication via separate handlers: functions that receive update details and overall bot context.

Here is a link to the python-telegram-bot GitHub (if they’re allowed) wiki page which has information on hosting

I've used Telegram and python-telegram-bot in the past, it's reasonably easy to use.

If you want a more powerful tool that also works crossplatform, then you look at software like git, bup or rdiff-backup. These are very powerful version control systems/backupsystems. However these tools are not the most user friendly. They don't come with a user interface and require some setup.

As others have said version control is your answer. I use git and I run completely independent of GitHub. I have a raspberry pi server that I have setup as my own remote. So I can work on my code on any computer, commit and push it to my server then I can pull it down on another machine and they will be perfectly in sync. This also means you will have multiple copies of the code, so if one computer gets wiped out, your remote (server) and other machines will still have mostly up to date copies of the code. If you push and pull code frequently the most work you lose is a day or so. If a laptop and a server go down, you have local a copy on your other machines. This setup has saved my butt dozens of times.

Install git

ReadMe gave us enough features to get started with our documentation. We could create and update our documentation when needed and without much effort, but we couldn’t collaborate as much as we needed and could only save one draft at a time. This was a major challenge because anyone could easily overwrite another’s work if they were working on the same file at the same time. ReadMe also had a flat file structure which was inconvenient to use. There was also no real Git integration into their CLI, so we had issues with document versioning and collaboration. Ultimately, this meant that docs were in the approval process for an unnecessary length of time and not everyone was able to make suggestions for improvement as they came up.

After downloading and installing Git on your computer, you may be asking yourself how to start using it effectively. I wrote this guide for myself a few weeks ago and thought about sharing it in some public platform in order to maybe help someone else, so here we go!

How we use Git download GIT from here,

If you don't know git, why you are here mate? So if you do know git and you use it almost every day so sometimes you google the git command that you don't use often. So here I am just asking for a git command that you use often with a single-line title, summary, and your GitHub username. So, comment down the git command. I want it just because I am making a gist that will contain useful commands so that people don't need to google it again and again.