ahriman/docs/faq.md
Evgeniy Alekseev 13121298f5 deprecate init/repo-init command
In current workflow you need to run setup to run init (because of
repository name), but you need to run init before setup (because of
repository tree rights).

New solution just add `Repo.init()` method call to setup subcommand
after config reload to make sure that repository name has been applied.
In addition chown method as well as setuid method for check_output have
been added.
2022-03-21 01:32:11 +03:00

16 KiB

FAQ

General topics

What is the purpose of the project?

This project has been created in order to maintain self-hosted Arch Linux user repository without manual intervention - checking for updates and building packages.

How do I install it?

TL;DR

yay -S ahriman
sudo ahriman -a x86_64 repo-setup --packager "ahriman bot <ahriman@example.com>" --repository "repository"
systemctl enable --now ahriman@x86_64.timer

Long answer

The idea is to install the package as usual, create working directory tree, create configuration for sudo and devtools. Detailed description of the setup instruction can be found here.

What does "architecture specific" mean? / How to configure for different architectures?

Some sections can be configured per architecture. The service will merge architecture specific values into common settings. In order to specify settings for specific architecture you must point it in section name.

For example, the section

[build]
build_command = extra-x86_64-build

states that default build command is extra-x86_64-build. But if there is section

[build:i686]
build_command = extra-i686-build

the extra-i686-build command will be used for i686 architecture.

How to use reporter/upload settings?

Normally you probably like to generate only one report for the specific type, e.g. only one email report. In order to do it you will need to have the following configuration:

[report]
target = email

[email]
...

or in case of multiple architectures and different reporting settings:

[report]
target = email

[email:i686]
...

[email:x86_64]
...

But for some cases you would like to have multiple different reports with the same type (e.g. sending different templates to different addresses). For these cases you will need to specify section name in target and type in section, e.g. the following configuration can be used:

[report]
target = email_1 email_2

[email_1]
type = email
...

[email_2]
type = email
...

Okay, I've installed ahriman, how do I add new package?

sudo -u ahriman ahriman package-add ahriman --now

--now flag is totally optional and just run repo-update subcommand after the registering the new package, Thus the extended flow is the following:

sudo -u ahriman ahriman package-add ahriman
sudo -u ahriman ahriman repo-update

AUR is fine, but I would like to create package from local PKGBUILD

TL;DR

sudo -u ahriman ahriman package-add /path/to/local/directory/with/PKGBUILD --now

Before using this command you will need to create local directory, put PKGBUILD there and generate .SRCINFO by using makepkg --printsrcinfo > .SRCINFO command. These packages will be stored locally and will be ignored during automatic update; in order to update the package you will need to run package-add command again.

But I just wanted to change PKGBUILD from AUR a bit!

Well it is supported also.

  1. Clone sources from AUR.
  2. Make changes you would like to (e.g. edit PKGBUILD, add external patches).
  3. Run sudo -u ahriman ahriman patch-add /path/to/local/directory/with/PKGBUILD.

The last command will calculate diff from current tree to the HEAD and will store it locally. Patches will be applied on any package actions (e.g. it can be used for dependency management).

Package build fails because it cannot validate PGP signature of source files

TL;DR

sudo -u ahriman ahriman key-import ...

How do I check if there are new commits for VCS packages?

Normally the service handles VCS packages correctly, but it requires additional dependencies:

pacman -S breezy darcs mercurial subversion

I would like to remove package because it is no longer needed/moved to official repositories

sudo -u ahriman ahriman package-remove ahriman

Also, there is command repo-remove-unknown which checks packages in AUR and local storage and removes ones which have been removed.

Remove commands also remove any package files (patches, caches etc).

There is new major release of %library-name%, how do I rebuild packages?

TL;DR

sudo -u ahriman ahriman repo-rebuild --depends-on python

You can even rebuild the whole repository (which is particular useful in case if you would like to change packager) if you do not supply --depends-on option.

However, note that you do not need to rebuild repository in case if you just changed signing option, just use repo-sign command instead.

Hmm, I have packages built, but how can I use it?

Add the following lines to your pacman.conf:

[repository]
Server = file:///var/lib/ahriman/repository/x86_64

(You might need to add SigLevel option according to the pacman documentation.)

I would like to serve the repository

Easy. For example, nginx configuration (without SSL) will look like:

server {
    listen 80;
    server_name repo.example.com;

    location / {
        autoindex on;
        root /var/lib/ahriman/repository;
    }
}

Example of the status page configuration is the following (status service is using 8080 port):

server {
    listen 80;
    server_name builds.example.com;

    location / {
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarder-Proto $scheme;

        proxy_pass http://127.0.0.1:8080;
    }
}

Docker image

We provide official images which can be found under arcan1s/ahriman repository. Docker image is being updated on each master commit as well as on each version. If you would like to use last (probably unstable build) you can use latest tag; otherwise you can use any version tag available.

The default action (in case if no arguments provided) is repo-update. Basically the idea is to run container, e.g.:

docker run --privileged -v /path/to/local/repo:/var/lib/ahriman arcan1s/ahriman:latest

--privileged flag is required to make mount possible inside container. In addition, you can pass own configuration overrides by using the same -v flag, e.g.:

docker run -v /path/to/local/repo:/var/lib/ahriman -v /etc/ahriman.ini:/etc/ahriman.ini.d/10-overrides.ini arcan1s/ahriman:latest

By default, it runs repo-update, but it can be overwritten to any other command you would like to, e.g.:

docker run arcan1s/ahriman:latest package-add ahriman --now

For more details please refer to docker FAQ.

Environment variables

The following environment variables are supported:

  • AHRIMAN_ARCHITECTURE - architecture of the repository, default is x86_64.
  • AHRIMAN_DEBUG - if set all commands will be logged to console.
  • AHRIMAN_FORCE_ROOT - force run ahriman as root instead of guessing by subcommand.
  • AHRIMAN_OUTPUT - controls logging handler, e.g. syslog, console. The name must be found in logging configuration. Note that if syslog (the default) handler is used you will need to mount /dev/log inside container because it is not available there.
  • AHRIMAN_PACKAGER - packager name from which packages will be built, default is ahriman bot <ahriman@example.com>.
  • AHRIMAN_PORT - HTTP server port if any, default is empty.
  • AHRIMAN_REPOSITORY - repository name, default is aur-clone.
  • AHRIMAN_REPOSITORY_ROOT - repository root. Because of filesystem rights it is required to override default repository root. By default, it uses ahriman directory inside ahriman's home, which can be passed as mount volume.
  • AHRIMAN_USER - ahriman user, usually must not be overwritten, default is ahriman.

You can pass any of these variables by using -e argument, e.g.:

docker run -e AHRIMAN_PORT=8080 arcan1s/ahriman:latest

Working with web service

Well for that you would need to have web container instance running forever; it can be achieved by the following command:

docker run -p 8080:8080 -e AHRIMAN_PORT=8080 -v /path/to/local/repo:/var/lib/ahriman arcan1s/ahriman:latest

Note about AHRIMAN_PORT environment variable which is required in order to enable web service. An additional port bind by -p 8080:8080 is required to pass docker port outside of container.

For every next container run use arguments -e AHRIMAN_PORT=8080 --net=host, e.g.:

docker run --privileged -e AHRIMAN_PORT=8080 --net=host -v /path/to/local/repo:/var/lib/ahriman arcan1s/ahriman:latest

Remote synchronization

Wait I would like to use the repository from another server

There are several choices:

  1. Easy and cheap, just share your local files through the internet, e.g. for nginx:

    server {
        location /x86_64 {
            root /var/lib/ahriman/repository/x86_64;
            autoindex on;
        }
    }
    
  2. You can also upload your packages using rsync to any available server. In order to use it you would need to configure ahriman first:

    [upload]
    target = rsync
    
    [rsync]
    remote = 192.168.0.1:/srv/repo
    

    After that just add /srv/repo to the pacman.conf as usual. You can also upload to S3 (e.g. Server = https://s3.eu-central-1.amazonaws.com/repository/x86_64) or to Github (e.g. Server = https://github.com/ahriman/repository/releases/download/x86_64).

How do I configure S3?

  1. Install dependencies:

    pacman -S python-boto3
    
  2. Create a bucket.

  3. Create user with write access to the bucket:

    {
        "Version": "2012-10-17",
        "Statement": [
            {
                "Sid": "ListObjectsInBucket",
                "Effect": "Allow",
                "Action": [
                    "s3:ListBucket"
                ],
                "Resource": [
                    "arn:aws:s3:::repository"
                ]
            },
            {
                "Sid": "AllObjectActions",
                "Effect": "Allow",
                "Action": "s3:*Object",
                "Resource": [
                    "arn:aws:s3:::repository/*"
                ]
            }
        ]
    }
    
  4. Create an API key for the user and store it.

  5. Configure the service as following:

    [upload]
    target = s3
    
    [s3]
    access_key = ...
    bucket = repository
    region = eu-central-1
    secret_key = ...
    

How do I configure Github?

  1. Create a repository.

  2. Create API key with scope public_repo.

  3. Configure the service as following:

    [upload]
    target = github
    
    [github]
    owner = ahriman
    password = ...
    repository = repository
    username = ahriman
    

Reporting

I would like to get report to email

  1. Install dependencies:

    yay -S python-jinja
    
  2. Configure the service:

    [report]
    target = email
    
    [email]
    host = smtp.example.com
    link_path = http://example.com/x86_64
    password = ...
    port = 465
    receivers = me@example.com
    sender = me@example.com
    user = me@example.com
    

I'm using synchronization to S3 and would like to generate index page

  1. Install dependencies:

    yay -S python-jinja
    
  2. Configure the service:

    [report]
    target = html
    
    [html]
    path = /var/lib/ahriman/repository/x86_64/index.html
    link_path = http://example.com/x86_64
    

After these steps index.html file will be automatically synced to S3

Web service

Readme mentions web interface, how do I use it?

  1. Install dependencies:

    yay -S python-aiohttp python-aiohttp-jinja2
    
  2. Configure service:

    [web]
    port = 8080
    
  3. Start the web service systemctl enable --now ahriman-web@x86_64.

I would like to limit user access to the status page

  1. Install dependencies 😊:

    yay -S python-aiohttp-security python-aiohttp-session python-cryptography
    
  2. Configure the service to enable authorization:

    [auth]
    target = configuration
    
  3. Create user for the service:

    sudo -u ahriman ahriman user-add --as-service -r write api
    

    This command will ask for the password, just type it in stdin; do not leave the field blank, user will not be able to authorize.

  4. Create end-user sudo -u ahriman ahriman user-add -r write my-first-user with password.

  5. Restart web service systemctl restart ahriman-web@x86_64.

I would like to use OAuth

  1. Create OAuth web application, download its client_id and client_secret.

  2. Guess what? Install dependencies:

    yay -S python-aiohttp-security python-aiohttp-session python-cryptography python-aioauth-client
    
  3. Configure the service:

    [auth]
    target = oauth
    client_id = ...
    client_secret = ...
    
    [web]
    address = https://example.com
    

    Configure oauth_provider and oauth_scopes in case if you would like to use different from Google provider. Scope must grant access to user email. web.address is required to make callback URL available from internet.

  4. Create service user:

    sudo -u ahriman ahriman user-add --as-service -r write api
    
  5. Create end-user sudo -u ahriman ahriman user-add -r write my-first-user. When it will ask for the password leave it blank.

  6. Restart web service systemctl restart ahriman-web@x86_64.

Other topics

How does it differ from %another-manager%?

Short answer - I do not know.

archrepo2

Don't know, haven't tried it. But it lacks of documentation at least.

  • Web interface.
  • No synchronization and reporting.
  • archrepo2 actively uses direct shell calls and yaourt components.
  • It has constantly running process instead of timer process (it is not pro or con).

repoctl

  • Web interface.
  • No reporting.
  • Local packages and patches support.
  • Some actions are not fully automated (e.g. package update still requires manual intervention for the build itself).
  • repoctl has better AUR interaction features. With colors!
  • repoctl has much easier configuration and even completion.
  • repoctl is able to store old packages.
  • Ability to host repository from same command vs external services (e.g. nginx) in ahriman.

repo-scripts

Though originally I've created ahriman by trying to improve the project, it still lacks a lot of features:

  • Web interface.
  • Better reporting with template support.
  • Synchronization features (there was only rsync based).
  • Local packages and patches support.
  • No dependency management.
  • And so on.

repo-scripts also have bad architecture and bad quality code and uses out-of-dated yaourt and package-query.

I would like to check service logs

By default, the service writes logs to /dev/log which can be accessed by using journalctl command (logs are written to the journal of the user under which command is run).

You can also edit configuration and forward logs to stderr, just change handlers value, e.g.:

sed -i 's/handlers = syslog_handler/handlers = console_handler/g' /etc/ahriman.ini.d/logging.ini

You can even configure logging as you wish, but kindly refer to python logging module configuration.

Html customization

It is possible to customize html templates. In order to do so, create files somewhere (refer to Jinja2 documentation and the service source code for available parameters) and put template_path to configuration pointing to this directory.

I did not find my question

Create an issue with type Question.