waja

a push request would be cool!

Running the CI pipeline on a forgejo runner fails actually with: ``` ::group::Install build dependencies [command]/usr/bin/docker exec dropbear bash -c apt-get build-dep -yq -t 'bullseye-backports' '/workspace/waja/action-debian-package/dropbear' || apt-get build-dep -yq...

hmmm ... seems like the directory is empty in the container: ``` ::group::Check sourceDirectory [command]/usr/bin/docker exec dropbear ls -la /workspace/waja/action-debian-package/dropbear total 8 drwxr-xr-x 2 root root 4096 Jan 4 18:36...

Actually, I suspect `valid_volumes` from [runners config](https://forgejo.org/docs/latest/admin/actions/#configuration). I'm looking into it.

I can confirm this issue: ``` # /tmp/check_running_kernel WARNING: Running kernel does not match on-disk kernel image: [Linux version 5.13.0-39-generic (buildd@lcy02-amd64-080) (gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0, GNU ld (GNU Binutils for...

Hi @hoellen, thanks for maintaining this great project. I think it would be nice to have the HPB shipped by default but (maybe for now) not enabled by default but...

> I vote for only adding the push location to the nginx config because there is an official HPB image already. Adding another image creates lot of additional hassle. See...

> Atm HPB ist working for me in the seperate container. @hathagat do you wonna share your docker compose config with us?

@hathagat the part I'm missing here is the push part. I'm still trying to run the `notify_push` image from https://hub.docker.com/r/icewind1991/notify_push/, which is basically https://github.com/nextcloud/notify_push. Following the suggestion on https://github.com/nextcloud/notify_push#push-server-is-not-a-trusted-proxy: >...

This project isn't active anymore. See https://github.com/hoellen/docker-nextcloud#migration-from-the-legacy-image