I did not experience such instability described in your comment. It is possible that your ISP has peering issues with forejo.ellis.link.

Also, I've hosted my projects on Codeberg before and the uptime is not that great.

suggest replacing source with one of the mirrors (e.g. https://codeberg.org/continuwuity/continuwuity), as cloning from forgejo.ellis.link times out all the time

It might be an issue if your server is running long enough and had frequent service installations. Every time a system user is assigned with a UID (2-1000), it does not release them even if the system user file is deleted.

Yes, we utilise the dynamic user feature to avoid UID starvation

UIDs are 32-bit numbers; I don't think adding one is a big deal. The main benefit of this is that you can mark files as permanently owned by this user between sessions without having to worry about changing UIDs.

It appears that pkgconf is a buildtime dependency as compilation of librocksdb-sys requires the pkg-config command.

Yes, we utilise the dynamic user feature to avoid UID starvation

This package should offer a stub in sysusers.d to create the conduwuit user, since currently the service file expects this user/group to exist:

u conduwuit - "continuwuity user"