Change sessions.rst formatting to be compliant with codebase's style

This commit is contained in:
tsujp 2018-02-06 19:15:55 +09:00
parent fc3f25cd5f
commit de29141277

View File

@ -50,7 +50,7 @@ Sessions and Heroku
-------------------
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 your
session file on a system with SQLite >= 3.8.2 your session file will not work
on Heroku's platform and will throw a corrupted schema error.
@ -62,7 +62,8 @@ a custom buildpack to install SQLite >= 3.8.2.
Generating Session File on a Heroku Dyno
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
**Do not restart your application Dyno at any point prior to retrieving your
.. warning::
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
result in a 24 hour rate limit ban**
@ -80,15 +81,15 @@ Using this scaffolded code we can start the authentication process:
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"
dropdown at the top right. Enter `bash` and wait for it to load.
dropdown at the top right. Enter ``bash`` and wait for it to load.
You will automatically be placed into your applications working directory.
So run your application `python app.py` and now you can complete the input
So run your application ``python app.py`` and now you can complete the input
requests such as "what is your phone number" etc.
Once you're successfully authenticated exit your application script with
CTRL + C and `ls` to confirm `login.session` exists in your current directory.
Now you can create a git repo on your account and commit `login.session` to
CTRL + C and ``ls`` to confirm ``login.session`` exists in your current directory.
Now you can create a git repo on your account and commit ``login.session`` to
that repo.
You cannot ssh into your Dyno instance because it has crashed, so unless you