|Max Mehl 8810dbf0a7||6 months ago|
|doc||2 years ago|
|fsfe_cd_front||6 months ago|
|tests||7 months ago|
|.dockerignore||3 years ago|
|.drone.yml||2 years ago|
|.gitignore||3 years ago|
|.isort.cfg||3 years ago|
|Dockerfile||7 months ago|
|Dockerfile-quality||7 months ago|
|LICENSE||7 months ago|
|MANIFEST.in||3 years ago|
|Makefile||7 months ago|
|Pipfile||2 years ago|
|Pipfile.lock||2 years ago|
|README.md||7 months ago|
|babel.cfg||4 years ago|
|docker-compose-quality.yml||7 months ago|
|docker-compose.yml||6 months ago|
|setup.py||7 months ago|
FSFE Community Database Frontend
The web user interface for the FSFE Community Database, visible through https://my.fsfe.org/
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 command line 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 Frontend.
fsfe-cd-front is a web application built with Flask. It provides a number of endpoints (called "views" in Flask) of the following categories:
Endpoints for interaction with the actual user: registering as a new user (
donate.py), paying online (
payonline.py), logging in and out (
login.py), and viewing as well as updating the personal settings (
Endpoints for handling predefined commands which can be executed by simply following a prepared link (
Endpoints for the automatic registration of incoming payments through PayPal or ConCardis (
Translations can be found in
fsfe_cd_front/translations/. Almost all strings are available in on .po file which can be edited with tools like Poedit.
In order to create a new language, just create the language's folder and an empty file messages.po, so for instance
fsfe_cd_front/translations/es/LC_MESSAGES/messages.po. Afterwards, run
make msgsupdate to fill this file with all strings used in the interface.
As soon as you have finished the translation, please run
make msgscompile. You can now commit the two changed files.
make commands (msasupdate and msgscompile), need to be run from the project's root folder.
The language displayed on my.fsfe.org is derived from your browser's language setting.
The source strings contain newlines (
\n) and empty spaces. You don't have to add those to your translation and can ignore such errors from Poedit.
doc contains more detailed documentation.