|Reinhard Müller be241dbbbd Fix issue with username change||2 days ago|
|bin||4 days ago|
|config||1 month ago|
|doc||2 months ago|
|fsfe_cd_back||2 days ago|
|tests||1 month ago|
|.dockerignore||2 months ago|
|.drone.yml||2 months ago|
|.gitignore||2 months ago|
|.isort.cfg||5 months ago|
|Dockerfile||4 days ago|
|Dockerfile-quality||4 months ago|
|LICENSE||6 months ago|
|MANIFEST.in||2 months ago|
|Makefile||1 month ago|
|Pipfile||3 months ago|
|Pipfile.lock||3 months ago|
|README.md||4 months ago|
|docker-compose-quality.yml||4 months ago|
|docker-compose.yml||5 months ago|
|setup.py||2 months ago|
The backend for the FSFE Community Database, including a Python interface to the data, a resource server for the frontend, and some command line tools used for manual data maintenance
The FSFE Community Database is a combined tool for donation management, administration of accounts for FSFE’s services, and opt-in based distribution of information emails.
All relevant data for these purposes is stored in a PostgreSQL database on the one hand and FSFE’s LDAP server on the other hand. Access to that data is encapsulated by the FSFE Community Database Backend (fsfe-cd-back), which provides both a set of commandline tools for manual administration tasks, and a protected RESTful(ish) network API to be used by other components.
The FSFE Community Database Authentication Server (fsfe-cd-auth) is an OpenID Connect Provider running on https://id.fsfe.org which authenticates a user against the LDAP server and then issues an access token which provides access to the authenticated user’s (and only the authenticated user’s) data though fsfe-cd-back’s API.
Finally, the FSFE Community Database Frontend is a web application through which the people stored in the database can manage their own data at https://my.fsfe.org. It sends users to fsfe-cd-auth to log in and then uses the user-bound access token returned from there to access the user’s data through fsfe-cd-back.
This repository contains the FSFE Community Database Backend. It essentially consists of three parts:
An Object-Relational Mapper (ORM) which turns database records into Python
objects and adds all the methods necessary to perform the tasks the FSFE
Community Database is built for. This layer is the core of the whole
structure. It is built with SQLAlchemy and resides in
A resource server with a REST-like API to allow data access for the other
components of fsfe-cd. All its access to the actual data goes through the
ORM. The resource server is implemented with Flask and can be found in
A set of command line tools for manual administration tasks, most of which
are only a thin wrapper around methods implemented in the ORM. They are
collected in the
doc contains more detailled documentation.