Selfhosted csolisr • 1 year ago • 100%

kbin.social

I'm currently trying to package /kbin for the [YunoHost](https://www.yunohost.org) system, and I already have a preliminary version [over here](https://github.com/csolisr/kbin_ynh). 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?

I'm currently trying to package /kbin for the [YunoHost](https://www.yunohost.org) system, and I already have a preliminary version [over here](https://github.com/csolisr/kbin_ynh). 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?

I only need two buttons, Ctrl + C and Ctrl + V. csolisr • 1 year ago • 100%

I'd just like to interject for a moment. What you're refering to as Lemmy, is in fact, a part of the Fediverse, or as I've recently taken to calling it, the Threadiverse. Lemmy is not a protocol unto itself, but rather another free software server of a fully interconnected Fediverse, made useful by the ActivityPub protocol as defined by the World Wide Web Consortium. Many computer users interact with a version of ActivityPub every day, without realizing it. Through a peculiar turn of events, the version of ActivityPub which is widely used today is often called Mastodon, or Lemmy, and many of its users are not aware that it is basically the ActivityPub system, developed by several independent projects such as Mastodon, Lemmy or Kbin. There really is a Lemmy, and these people are using it, but it is just a part of the Fediverse they use. Lemmy is the implementation: the program in the server that allocates the messages to the other servers that run in the Fediverse. The implementation is an essential part of the network, but isolated by itself; it can only interact in the context of a complete federated network. Lemmy is normally used in combination with either instances of itself, or of similar projects of the Threadiverse such as Kbin: the whole network is basically ActivityPub with Lemmy as a node. All the so-called Lemmy servers are really nodes of the Fediverse!