this post was submitted on 19 Jun 2023
3 points (100.0% liked)

Selfhosted

39251 readers
215 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
3
Currently trying to package /kbin for YunoHost, can you please check my repo? (kbin.social)
submitted 1 year ago by [email protected] to c/[email protected]
0 comments fedilink hide all child comments
 

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?

no comments (yet)
sorted by: hot top controversial new old
there doesn't seem to be anything here