GitLab

It matters behind a reverse-proxy.

Web_election.Make and SITE.import_election now return something that
can be discarded without side-effects on the running server.

Rationale: we want to be able to perform additional checks in the
caller of SITE.import_election. This will be useful when online
creation of elections is possible.

As a side-effect, they do no longer need to fit into memory. This
fixes "TODO: streaming".

Drop the property from WEB_PARAMS and import_election arguments. It is
up to the caller of import_election to call add_featured_election
afterwards.

When the login service is used for the first time, it asks for a
password database. For now, it is the administrator's responsibility
to do it before advertising the election.

 - do not show any login box on the site home page
 - add a link to site admnistration page to the generic footer

SITE.register_election takes only parsed stuff.

Move code specific to a group implementation there, and use it
everywhere else.

They do not behave as expected on serialized JSON objects. Instead,
directly export a reader and a writer as needed.

The "p" property is specific to finite fields anyway, so there is no
gain in abstracting the group element type in it.

In each directory, always open in the following order:
 1. third-party libraries
 2. serializable
 3. signatures
 4. common

Also, always open modules from lib/* before. This order is reflected
in *.mllib files.

Additionally, open more frequently serialization modules.