Files
ahriman/recipes/sign
Evgenii Alekseev c6306631e6 fix: careful handling of file permissions during initialization
It has been found that during cold start (e.g. in docker container),
some permissions are invalid. In order to handle that, some operations
are not guarded with RepositoryPaths.preserve_root guard

In addition, it has been also found that in some cases (e.g. web server
start) migrations are performed on empty repository identifier which may
lead to wrong data (see also 435375721d),
as well as some unexpected results during database operations. In order
to handle that, now all watcher instances have their own databases (and
configurations)
2025-07-11 17:13:37 +03:00
..
2023-12-20 10:00:12 +02:00
2023-12-20 10:00:12 +02:00
2023-12-20 10:00:12 +02:00

Sign

This example uses generated key. It can be generated as:

gpg --full-generate-key
gpg --export-secret-keys -a <...> > repository-sign.gpg
  1. Setup repository named ahriman-demo with architecture x86_64.
  2. Sing repository database with the distributed key.
  3. Start service in daemon mode with periodic (once per day) repository update.
  4. Repository is available at http://localhost:8080/repo.