78 lines
1.6 KiB
Markdown
78 lines
1.6 KiB
Markdown
# Lacre administration
|
|
|
|
## Command-line tool
|
|
|
|
There's a little tool for administrators. As long as Lacre Python packages
|
|
are available via `PYTHONPATH`, you can use it like this:
|
|
|
|
```sh
|
|
python -m lacre.admin -h
|
|
```
|
|
|
|
Of course `-h` displays some help.
|
|
|
|
**Note:** Help output includes information about the configuration file being
|
|
in use, which may be useful at times.
|
|
|
|
**Note:** You can also use a tiny shell wrapper around this tool, see
|
|
`bin/lacreadm`.
|
|
|
|
|
|
## Initialising database schema
|
|
|
|
If you want to initialise Lacre's database (which is also used by the
|
|
frontend), run:
|
|
|
|
```sh
|
|
python -m lacre.admin database -i
|
|
```
|
|
|
|
|
|
## Inspecting key confirmation queue
|
|
|
|
To find out how many keys are waiting to be confirmed, run:
|
|
|
|
```sh
|
|
python -m lacre.admin queue
|
|
```
|
|
|
|
To see identities (emails) waiting for confirmation, use `--list` (or `-l`)
|
|
option:
|
|
|
|
```sh
|
|
python -m lacre.admin queue -l
|
|
```
|
|
|
|
To delete one of these emails, use `--delete` (or `-d`) option:
|
|
|
|
```sh
|
|
python -m lacre.admin queue -d malory@example.org
|
|
```
|
|
|
|
## Inspecting identities registered
|
|
|
|
To list all identities, run:
|
|
|
|
```sh
|
|
python -m lacre.admin identities -a
|
|
```
|
|
|
|
To preview a particular identity, run:
|
|
|
|
```sh
|
|
python -m lacre.admin identities -e alice@example.com
|
|
```
|
|
|
|
## Importing identities from existing GnuPG keyring
|
|
|
|
If you already have a GnuPG keyring with your users' public keys or for some
|
|
reason Lacre's identity database needs to be re-populated with identities,
|
|
there's a command to do that:
|
|
|
|
```sh
|
|
python -m lacre.admin import -d /path/to/gnupg/directory
|
|
```
|
|
|
|
If you want to just re-populate the database, Lacre can remove all identities
|
|
prior to importing keys -- just add `-r` flag.
|