Our beloved assistant, he only has a few simple tasks here at PyDis, using two halves of a coconut to simulate the hoof-beats of King Arthur's non-existent horse is not one of them!
Python will send Patsy message data, including the content, and Patsy will transform and store that data in postgres.
With this data we plan to inspect what topics get asked about often in help channels, along with which ones go un-answered the most.
To be GDPR compliant, Python will also give an opt-out command, which will be stored by Patsy, and will be used to determine which messages to store, and which to drop.
Deleted messages will always be deleted from the data set, regardless of opt-out status.
Patsy requires the following environment variables to be present in a .env file, found at the project root.
The following environment variables is only required in production
DATABASE_URL - An asyncpg connection string to the postgres database postgresql+asyncpg://pypatsy:pypatsy@postgres:5432/pypatsy.
SECRET_KEY - A long random string, used to lock down endpoints with auth.
The following environment variables are only required in dev.
DEBUG - true or false. Whether to enable debug mode in the service.
Once your .env file is setup, you can start this service by running docker-compose up in the root directory.
You can test it's running be navigating to http://127.0.0.1:8000/ping
With the project running, open another terminal and run poetry run task revision "Migration message here."
This will create a migration file in the path alembic_conf/versions. Make sure to check it over, and fix any flake8 issues.
Before committing make sure to run poetry install and then poetry run task precommit to install the project dependencies and the pre-commit hook.
