LonamiWebs/Telethon
1
1
Fork 0
mirror of https://github.com/LonamiWebs/Telethon.git synced 2025-08-06 05:00:23 +03:00
Code Issues Packages Projects Releases Wiki Activity

things

Browse Source
This commit is contained in:
Lonami Exo 2018-02-06 11:20:35 +01:00
parent de29141277
commit 82e25302d7
1 changed files with 12 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
readthedocs/extra/advanced-usage/sessions.rst
View File

@ -50,9 +50,9 @@ Sessions and Heroku
------------------- -------------------
You probably have a newer version of SQLite installed (>= 3.8.2). Heroku uses You probably have a newer version of SQLite installed (>= 3.8.2). Heroku uses
SQLite 3.7.9 which does not support ``WITHOUT ROWID``. So, If you generated your SQLite 3.7.9 which does not support ``WITHOUT ROWID``. So, if you generated
session file on a system with SQLite >= 3.8.2 your session file will not work your session file on a system with SQLite >= 3.8.2 your session file will not
on Heroku's platform and will throw a corrupted schema error. work on Heroku's platform and will throw a corrupted schema error.
There are multiple ways to solve this, the easiest of which is generating a There are multiple ways to solve this, the easiest of which is generating a
session file on your Heroku dyno itself. The most complicated is creating session file on your Heroku dyno itself. The most complicated is creating
@ -64,8 +64,8 @@ Generating Session File on a Heroku Dyno
.. warning:: .. warning::
Do not restart your application Dyno at any point prior to retrieving your Do not restart your application Dyno at any point prior to retrieving your
session file. Constantly creating new session files from Telegram's API will session file. Constantly creating new session files from Telegram's API
result in a 24 hour rate limit ban** will result in a 24 hour rate limit ban.
Due to Heroku's ephemeral filesystem all dynamically generated Due to Heroku's ephemeral filesystem all dynamically generated
files not part of your applications buildpack or codebase are destroyed upon files not part of your applications buildpack or codebase are destroyed upon
@ -75,9 +75,7 @@ Using this scaffolded code we can start the authentication process:
.. code-block:: python .. code-block:: python
client = TelegramClient('login.session', api_id, api_hash, client = TelegramClient('login.session', api_id, api_hash).start()
update_workers=1, spawn_read_thread=False)
client.start()
At this point your Dyno will crash because you cannot access stdin. Open your At this point your Dyno will crash because you cannot access stdin. Open your
Dyno's control panel on the Heroku website and "run console" from the "More" Dyno's control panel on the Heroku website and "run console" from the "More"
@ -88,10 +86,10 @@ So run your application ``python app.py`` and now you can complete the input
requests such as "what is your phone number" etc. requests such as "what is your phone number" etc.
Once you're successfully authenticated exit your application script with Once you're successfully authenticated exit your application script with
CTRL + C and ``ls`` to confirm ``login.session`` exists in your current directory. CTRL + C and ``ls`` to confirm ``login.session`` exists in your current
Now you can create a git repo on your account and commit ``login.session`` to directory. Now you can create a git repo on your account and commit
that repo. ``login.session`` to that repo.
You cannot ssh into your Dyno instance because it has crashed, so unless you You cannot ``ssh`` into your Dyno instance because it has crashed, so unless
programatically upload this file to a server host this is the only way to get you programatically upload this file to a server host this is the only way to
it off of your Dyno. get it off of your Dyno.