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?
Agree with other commenter, if you are looking for packaging maintainers, the official forum is probably your best bet. They will have more domain-specific knowledge, and I’ve personally never used or packaged anything from Yunohost. If you’re looking for help it would also be a good idea to create new Github issues on each of the items you’re having trouble with, so potential contributors will know in detail what exactly they need to fix. Highlighting what the problems are in this post here is a good first step.