I'm currently trying to package /kbin for the YunoHost system, and I already have a preliminary version over here. However, I'm stuck in a few implementation details, namely:
- YunoHost expects the package to have a stable tarball release every so often. /kbin is evidently a rolling release, as there are no tags and no releases in the repository.
- YunoHost's tools are mostly based on GitHub, unfortunately. That means that the script used to automatically fetch a new release from the repository would only work if the source code was hosted on GitHub itself, not on Codeberg.
- Several items (the .env file, Composer, Symfony, Redis, Doctrine to configure the database, Yarn, RabbitMQ, Supervisor, and the initial configuration of user and password) require a certain amount of manual intervention which I still haven't figured how to build.
- The Nginx configuration recommended by the developer uses a sub-folder "/public", whereas the default Nginx template expects the application to run directly from root (or to reconfigure it, but the documentation doesn't quite explain how to do so!)
Can somebody with enough experience on the building process help me with those issues?
So, in case we have to take a side, would you rather get banned from Beehaw, or from Lemmy World?