Skip to main content

An API for interacting with the Tahrir database

Project description

Tahrir-API

API for interacting with the Tahrir database. Based on the Tahrir database model written by Ralph Bean. There are two classes that can be used in this module. The first is the TahrirDatabase class located in tahrir_api.dbapi and the second is the database model located in tahrir_api.model. The TahrirDatabase class is a high level way to interact with the database. The model is used for a slightly more low level way of interacting with the database. It allows for custom interactions with the database without having to use the TahrirDatabase class.

Development

System Requirements

Before getting started, ensure your system meets the following requirements:

Software Requirements

  • Python: 3.9 or higher

  • Poetry: Latest version for dependency management

  • Database: PostgreSQL 9.6+ (recommended) or SQLite (basic development)

  • Git: For version control

Operating System Requirement

  • Fedora Linux: Latest non-EOL versions

Note: Other distributions may work, but are not officially supported. The maintainers may not be able to assist with platform-specific issues on non-Fedora systems.

Project Setup

  1. Ensure that the necessary packages are installed:

$ sudo dnf install -y python3 python3-pip python3-devel poetry gcc krb5-devel git
  1. Clone your fork to the local storage and make it your current working directory:

$ git clone https://github.com/fedora-infra/tahrir-api.git
$ cd tahrir-api
  1. Create a virtual environment and activate it for installing project dependencies:

$ python3 -m venv venv
$ source venv/bin/activate
  1. Install project dependencies:

(venv) $ poetry check
(venv) $ poetry install

Database Setup

  1. Create a directory for storing the Tahrir database snapshot:

(venv) $ cd ..
(venv) $ mkdir badges-database
(venv) $ cd badges-database
  1. Download and extract the Tahrir database snapshot:

(venv) $ wget https://infrastructure.fedoraproject.org/infra/db-dumps/tahrir.dump.xz
(venv) $ unxz tahrir.dump.xz
  1. Create directories for persistent data and the database dump:

(venv) $ mkdir data dump
(venv) $ mv tahrir.dump dump/
  1. Pull the PostgreSQL container image:

(venv) $ podman pull docker.io/library/postgres:15
  1. Start the database container (be sure to rename the username and paths based on your development environment):

(venv) $ podman run \
    --name badges-database \
    --env POSTGRES_USER=badgesdb \
    --env POSTGRES_PASSWORD=badgesdb \
    --env POSTGRES_DB=badgesdb \
    --env PGDATA=/var/lib/postgresql/data/pgdata \
    --volume /home/username/Projects/badges-database/data:/var/lib/postgresql/data:Z \
    --volume /home/username/Projects/badges-database/dump:/badgesdb:Z \
    --publish 5432:5432 \
    --restart unless-stopped \
    --detach docker.io/library/postgres:15
  1. Once the database container has started, log in to the interactive shell using the password to begin importing the extracted dump:

(venv )$ podman pull docker.io/library/postgres:15
(venv )$ podman run \
  1. Execute the following SQL commands to create roles, load the database dump, and grant the needed access:

badgesdb=# create role "tahrir" with inherit nocreatedb nocreaterole noreplication nosuperuser valid until 'infinity' login password 'tahrir';
badgesdb=# create role "tahrir-readonly" with nocreatedb inherit nocreaterole noreplication nosuperuser valid until 'infinity' login password 'tahrir-readonly';
badgesdb=# \i badgesdb/tahrir.dump
badgesdb=# grant connect on database tahrir to "tahrir";
badgesdb=# grant all on all tables in schema public to "tahrir";
badgesdb=# grant all on all sequences in schema public to "tahrir";
badgesdb=# revoke create on schema public from public;
  1. Exit out of the interactive shell and log back in using the newly created credentials:

(venv )$ podman exec -ti badges-database psql --username badgesdb --password
  1. Verify the database setup:

(venv )$ tahrir=> \dt+

Run the tests

  1. Download and install tox:

(venv) $ cd ./tahrir-api
(venv) $ sudo dnf install tox
  1. Run the tests with tox:

(venv) $ tox

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

tahrir_api-1.5.3.tar.gz (49.3 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

tahrir_api-1.5.3-py3-none-any.whl (56.3 kB view details)

Uploaded Python 3

File details

Details for the file tahrir_api-1.5.3.tar.gz.

File metadata

  • Download URL: tahrir_api-1.5.3.tar.gz
  • Upload date:
  • Size: 49.3 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.13.14

File hashes

Hashes for tahrir_api-1.5.3.tar.gz
Algorithm Hash digest
SHA256 db0f75e85639e0f192af178cff6a3785373f5bd790918a41b69a1feb8676b405
MD5 28c09fd11ec13c129a73969d7cfc0dbd
BLAKE2b-256 61106c9ecb243252cd042a890f767844c86fe51c1d07dde8ce3fea9529ba59c5

See more details on using hashes here.

Provenance

The following attestation bundles were made for tahrir_api-1.5.3.tar.gz:

Publisher: main.yml on fedora-infra/tahrir-api

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file tahrir_api-1.5.3-py3-none-any.whl.

File metadata

  • Download URL: tahrir_api-1.5.3-py3-none-any.whl
  • Upload date:
  • Size: 56.3 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.13.14

File hashes

Hashes for tahrir_api-1.5.3-py3-none-any.whl
Algorithm Hash digest
SHA256 ff315b32d0a38ae9cf7ec86604ba3b797605f6b7ddda334913fcfcdd1d2d8131
MD5 98eb3f3addc6e51b13fe8fad0d69e56a
BLAKE2b-256 2ace22840560f0d058ba0254b6beeddcc675af33358c68468c041ffe7de534a5

See more details on using hashes here.

Provenance

The following attestation bundles were made for tahrir_api-1.5.3-py3-none-any.whl:

Publisher: main.yml on fedora-infra/tahrir-api

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page