Files
ahriman/recipes/i686
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
2023-12-20 10:00:12 +02:00
2023-12-20 10:00:12 +02:00

i686

This example uses hybrid setup from FAQ, because archlinux32 has outdated devtools package. So it distributes custom makepkg.conf and pacman.conf (which are copied from archlinux32 package) and builds custom image with archlinux32 keyring.

  1. Create user demo with password from AHRIMAN_PASSWORD environment variable.
  2. Build image from distributed Dockerfile.
  3. Setup repository named ahriman-demo with architecture i686.
  4. Start web server at port 8080.
  5. Repository is available at http://localhost:8080/repo.