nxy irc bot
jkhsjdhjs
e03f5d0a43
This only works on the second database interaction, since psycopg2 only notices that
the connection is gone, when a query is executed.
So in the common case reconnect works as follows:
- some bot method calls a cursor function like .execute(), .fetchone(), etc.
- this raises an error if the connection is broken
- if following code then requests a new cursor, this will also fail since psycopg2
now knows that the connection is gone
- the error is caught in storage.DBConn.cursor(), a new connection will be set up
of which a new cursor is yielded
If the error happens in connection.commit() or .rollback() instead we can instantly
reconnect since these methods are wrapped.
So why not wrap the cursor methods as well?
Consider the following example:
A query is the last thing that was executed on a cursor.
The database connection is lost.
Now .fetchone() is called on the cursor.
We could wrap .fetchone() and reconnect, but we'd have to use a new cursor since
cursors are linked to connections. And on this new cursor .fetchone() wouldn't
make any sense, since we haven't executed a query on this cursor.
|
||
|---|---|---|
| bot | ||
| files | ||
| .gitignore | ||
| FORMATTING.md | ||
| README.md | ||
| requirements.txt | ||
| TODOs | ||
| tox.ini | ||
PROJECT ABANDONED
Installation
Open psql as user postgres:
psql -U postgres
Create a user with password, allowed to login and a database:
CREATE ROLE nxy WITH ENCRYPTED PASSWORD 'your-password';
ALTER ROLE nxy LOGIN;
CREATE DATABASE nxy_prod OWNER nxy;
\c nxy_prod
CREATE EXTENSION citext;
\q
Apply database schema and optionally restore a dump:
psql -U nxy -d nxy_prod < nxy/files/schema.sql
psql -U nxy -d nxy_prod < path/to/dump.sql
Clone git repo, create virtual env, activate it and install dependencies:
git clone https://gitfap.de/mrhanky/nxy.git
python3 -m venv env
source env/bin/activate
pip install -U -r nxy/requirements.txt
Copy sample configs to $HOME and edit them:
cp nxy/files/{.env,config.json} .
vim .env config.json
Running as Service
Enable linger for the bot user (so it starts at boot and keeps running), install and activate systemd unit:
sudo loginctl enable-linger nxy
mkdir -p $HOME/.config/systemd/user
ln -fs $HOME/nxy/files/nxy-bot.service $HOME/.config/systemd/user
systemctl --user enable --now nxy-bot.service
Install and activate timer for database dumps:
ln -fs $HOME/nxy/files/nxy-db-dump.{timer,service} $HOME/.config/systemd/user
systemctl --user enable --now nxy-db-dump.timer
Running as Standalone in Development Mode
For development set the BOT_DEV variable:
export BOT_DEV=
Then add the current git repository to your python path:
export PYTHONPATH=<git repository>:$PYTHONPATH
Finally run nxy:
python3 -m bot