Files
ahriman/recipes
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

Recipes

Collection of the examples of docker compose configuration files, which covers some specific cases. Not for production use.

Configurations

  • Check: double process service; one with periodic checks (automatic build disabled) and other one is with the web service.
  • Daemon: service with periodic repository checks.
  • Distributed: cluster of three nodes, one with web interface and two workers which are responsible for build process.
  • Distributed manual: same as distributed, but two nodes and update process must be run on worker node manually.
  • i686: non-x86_64 architecture setup.
  • Index: repository with index page generator enabled.
  • Multi repo: run web service with two separated repositories.
  • OAuth: web service with OAuth (GitHub provider) authentication enabled.
  • PAM: web service with PAM authentication enabled.
  • Pull: normal service, but in addition with pulling packages from another source (e.g. GitHub repository).
  • Sign: create repository with database signing.
  • Web: simple web service with authentication enabled.