|Brume 935c0a9b54||1 month ago|
|export||3 months ago|
|src||1 month ago|
|.gitignore||3 months ago|
|Cargo.lock||1 month ago|
|Cargo.toml||1 month ago|
|LICENSE||3 months ago|
|README.md||3 months ago|
|config.toml.sample||3 months ago|
|screenshot.png||3 months ago|
Set of administration tools for 42l’s infrastructure
This software is an interface customized to 42l’s administrative needs. It is meant for internal use.
Though, you can see how do we manage our database and which tools we use to operate.
Because during a whole year, validating a subscription was done like this:
docker exec -it postgres-db psql <credentials> INSERT INTO "adhesions" (user_id, adh_date) VALUES (<user_id>, '<ex:2020-01-01>');
Silly, huh? After the 50th subscriber it was getting tiring, so here’s a backend software to do exactly the same thing, but without writing SQL queries, and with a friendly interface.
We also need to watch out for mailbox activities easily and without harming our users’ privacy, in order to react promptly if we get spammed ; so monitoring tools had been integrated into it.
encrypted_adresses = truein the configuration file.
As it is now, it can’t be used by other organizations to handle subscriptions. The mail monitoring feature might work, though.
I doubt this software will ever be compatible and reusable easily, because it has been especially made for 42l’s infrastructure – and every single association manages subscriptions in their own way.
Currently the software takes approximately 2k lines of code.
The functions location (in files / folders) needs to be rearranged, the overall code quality isn’t very good, even though clippy has been used to improve it a little.
Also, error handling is quite poor in this software, because it’s meant for sysadmins and/or developers and we assume that they know what they do. If you are unsatisified with this, PRs are welcome.