Limnoria/Limnoria-doc
1
0
Fork 0
mirror of https://github.com/Limnoria/Limnoria-doc.git synced 2025-04-04 14:29:46 +00:00
Code Issues Packages Projects Releases Wiki Activity

install & systemd: Mention how to setup with a virtualenv

Browse Source
This commit is contained in:
Valentin Lorentz
2023-04-29 10:45:42 +02:00
committed by Val Lorentz
parent 7cc6b1f9f8
commit ea060a65d5
2 changed files with 22 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
use/install.rst
View File

@ -89,6 +89,12 @@ Then Limnoria itself::
If you have an error saying ``No module named pip``, install ``pip`` using
your package manager (the package is usually named ``python3-pip``).
If you have an error about ``externally-managed-environment``, you need to setup
a virtualenv first, then re-run the commands above::
python3 -m venv /opt/venvs/limnoria # creates a virtualenv at the given path
. /opt/venvs/limnoria/bin/activate # enables the virtualenv in the current shell
Local installation (without root access)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@ -109,6 +115,12 @@ You might need to add $HOME/.local/bin to your PATH.::
If you have an error saying ``No module named pip``, install ``pip`` using this
guide: https://pip.pypa.io/en/stable/installing/
If you have an error about ``externally-managed-environment``, you need to setup
a virtualenv first, then re-run the commands above::
python3 -m venv ~/.venvs/limnoria # creates a virtualenv at the given path
. ~/.venvs/limnoria/bin/activate # enables the virtualenv in the current shell
.. _initial-configuration:
Configuration

10
use/supybot-botchk.rst
View File

@ -39,6 +39,16 @@ following content replacing things were suitable::
[Install]
WantedBy=multi-user.target
:file:`/usr/local/bin/supybot` should be the path where you installed Limnoria.
Typically, this is:
* :file:`/usr/local/bin/supybot` if installed as root without a virtualenv
* :file:`/opt/venvs/limnoria/bin/supybot` if installed as root with a virtualenv
as :file:`/opt/venvs/limnoria/`
* :file:`/home/BOTUSERNAME/.local/bin/supybot` if installed as non-root without a virtualenv
* :file:`/home/BOTUSERNAME/.venvs/limnoria/bin/supybot` if installed as non-root with a virtualenv
as :file:`~/.venvs/limnoria/`
Now you should run ``systemctl daemon-reload`` to make systemd aware
of changed files and ``systemctl enable <BOTNAME>.service`` to make the
bot start on boot etc. and ``systemctl start <BOTNAME>.service`` to start