[05:43:39]
<Yunohost Git/Infra notifications> [apps] tituspijean deleted branch add-to-wishlist-backdrop-cms
[07:24:33]
<Yunohost Git/Infra notifications> xmgz forked apps to [xmgz/apps](https://github.com/xmgz/apps)
[07:44:33]
<Yunohost Git/Infra notifications> [apps] xmgz opened [pull request #2699](https://github.com/YunoHost/apps/pull/2699): add phanpy to catalog
[07:51:08]
<Yunohost Git/Infra notifications> [apps] xmgz [commented](https://github.com/YunoHost/apps/pull/2699#issuecomment-2469819633) on [issue #2699](https://github.com/YunoHost/apps/pull/2699) add phanpy to catalog: ok, added **phanpy** to Catalog. Please tell me if further action is expected from my side **before** the app is actual...
[07:56:35]
<ghose> 😬so we a have a bot to bring here github comments 🤭
[08:17:01]
<Yunohost Git/Infra notifications> [apps] OniriCorpe changes_requested [pull request #2699](https://github.com/YunoHost/apps/pull/2699#pullrequestreview-2428847505) add phanpy to catalog
[08:17:02]
<Yunohost Git/Infra notifications> [apps] OniriCorpe [commented](https://github.com/YunoHost/apps/pull/2699#discussion_r1837654890) on pull request #2699 add phanpy to catalog: suggestion
[08:18:08]
<Yunohost Git/Infra notifications> [apps] OniriCorpe approved [pull request #2699](https://github.com/YunoHost/apps/pull/2699#pullrequestreview-2428850055) add phanpy to catalog
[08:19:44]
<Yunohost Git/Infra notifications> [apps] OniriCorpe merged [pull request #2699](https://github.com/YunoHost/apps/pull/2699): add phanpy to catalog
[08:19:44]
<Yunohost Git/Infra notifications> [apps] OniriCorpe pushed 1 commit to master: add phanpy to catalog (#2699) * add phanpy to apps.toml new app for the catalog * phanpy logo upload .png logo 400x4... ([3bf80255](https://github.com/YunoHost/apps/commit/3bf8025514f42df55b0b6ff4913e09f9c034cc5b))
[08:20:27]
<Yunohost Git/Infra notifications> [apps] yunohost-bot pushed 1 commit to master: Automatically add dates to the catalog files ([addf593a](https://github.com/YunoHost/apps/commit/addf593a905c8b5198b1a3cacc1591299eb42036))
[11:28:32]
<orhtej2> Given one can no longer install YNH on `bullseye`, the requirement for newly packaged apps is only `bookworm` compatibility?
[11:29:55]
<orhtej2> > <@yunohostinfra:matrix.org> [apps] xmgz [commented](https://github.com/YunoHost/apps/pull/2699#issuecomment-2469819633) on [issue #2699](https://github.com/YunoHost/apps/pull/2699) add phanpy to catalog: ok, added **phanpy** to Catalog. Please tell me if further action is expected from my side **before** the app is actual...
catalog will rebuild automatically in a couple of hours and the app should be listed [here](https://apps.yunohost.org/catalog?search=phanpy) then
[12:36:39]
<Aleks (he/him/il/lui)> > Given one can no longer install YNH on `bullseye`, the requirement for newly packaged apps is only `bookworm` compatibility?
It can still be installed using https://install.yunohost.org/bullseye and there's probably still >50% of Yunohosts in the wild on bullseye but yeah it doesnt make too much sense either to package new stuff for bullseye
[12:56:14]
<tituspijean> > <@ghose:tchncs.de> 😬so we a have a bot to bring here github comments 🤭
only on some repos, YunoHost/apps is one of them :)
[12:59:03]
<orhtej2> > <@Alekswag:matrix.org> It can still be installed using https://install.yunohost.org/bullseye and there's probably still >50% of Yunohosts in the wild on bullseye but yeah it doesnt make too much sense either to package new stuff for bullseye
is that 'legacy' install linked anywhere in the docs?
[13:46:05]
<Salamandar> > is that 'legacy' install linked anywhere in the docs?
hmmm not sure no
[14:50:59]
<Aleks (he/him/il/lui)> it's feature that this feature is undocumented 🙃
[16:24:37]
<Thomas> I receive more and more issues about `Error: PostgreSQL Authentication Failed for User '$app'` (first with Funkwhale, but now with FitTrackee too). https://github.com/YunoHost-Apps/fittrackee_ynh/issues/90
Isn’t the helper supposed to adapt the postgres conf automatically or do I have to check that during the install/upgrade/restore scripts?
[16:27:25]
<orhtej2> > <@thovi98:matrix.org> I receive more and more issues about `Error: PostgreSQL Authentication Failed for User '$app'` (first with Funkwhale, but now with FitTrackee too). https://github.com/YunoHost-Apps/fittrackee_ynh/issues/90
> Isn’t the helper supposed to adapt the postgres conf automatically or do I have to check that during the install/upgrade/restore scripts?
Var was not replaced?
[16:28:13]
<Thomas> Sorry yes it is, it was to that it happens on different apps
[16:32:14]
<Thomas> It’s more about the postgres conf where the default configuration for password is `peer` and we have to change it to `md5` (I think the helpers did that because for me I’ve never had this issue, but it may be related the install method of Yunohost or idk?)
[16:33:46]
<Thomas> Another thread was this one: https://forum.yunohost.org/t/funkwhale-installation-fails/27504/14?u=tho
[16:34:36]
<Aleks (he/him/il/lui)> yeah for some reason in yunohost regenconf we have:
```
# force all user to connect to local databases using hashed passwords
# https://www.postgresql.org/docs/current/static/auth-pg-hba-conf.html#EXAMPLE-PG-HBA.CONF
# Note: we can't use peer since YunoHost create users with nologin
# See: https://github.com/YunoHost/yunohost/blob/unstable/data/helpers.d/user
local pg_hba=/etc/postgresql/$PSQL_VERSION/main/pg_hba.conf
ynh_replace_string --match_string="local\(\s*\)all\(\s*\)all\(\s*\)peer" --replace_string="local\1all\2all\3md5" --target_file="$pg_hba"
```
[16:36:31]
<Thomas> Ah yes okay it’s in the regenconf, good to know
[16:36:47]
<Thomas> But for some reasons it doesn’t seem to always work
[16:36:59]
<Thomas> I will ask to regenconf on the FitTrackee issue, we will see
[16:37:02]
<Thomas> Thank you
[18:25:48]
<Carlos Solís> Hello everyone, I just managed to manually install Molly-socket using the manual installation guide: https://github.com/mollyim/mollysocket/blob/main/INSTALL.md What would it take to turn that guide into a YNH installation script?
[18:26:58]
<Carlos Solís> It needs downloading some files and editing a systemd service script, then running a few commands and opening a port, but otherwise it doesn't seem particularly difficult to configure
[18:42:06]
<Aleks (he/him/il/lui)> we have a web interface to create a draft of a yunohost package after filling a few questions : https://appgenerator.yunohost.org/
[18:42:20]
<Aleks (he/him/il/lui)> it's still a bit "rough" on edges and needs polishing but feel free to try it out
[19:32:18]
<eric_G> appgenerator 🤖 it is quite usable
[19:34:30]
<Aleks (he/him/il/lui)> hmmm to me section 7 and 9 could be polished somehow 😅 i mean i-dont-remember-who tried to generate a static app but there was some weird blocks with non-existent specific app config / cron job etc (or maybe the person did check the option even though they were not necessary?)
[19:43:55]
<Aleks (he/him/il/lui)> (i should test it myself oneday 😬)
[19:44:24]
<Aleks (he/him/il/lui)> (just like yunohost ? have you heard of it ? some people say you can deploy your server and a bunch of apps in just a few hours ! i should give it a try someday)
[20:03:19]
<ghose> > <@csolisr:azkware.net> It needs downloading some files and editing a systemd service script, then running a few commands and opening a port, but otherwise it doesn't seem particularly difficult to configure
yes, try **appgenerator**, at least you get basic strucuture for the package.
[20:04:14]
<ghose> > <@Alekswag:matrix.org> it's still a bit "rough" on edges and needs polishing but feel free to try it out
ex.: it adds `--src_path=` that then leads to some errors
[20:19:19]
<eric_G> > <@ghose:tchncs.de> ex.: it adds `--src_path=` that then leads to some errors
this should be fixed with https://github.com/YunoHost/appgenerator/pull/9
[20:25:30]
<Yunohost Git/Infra notifications> [appgenerator] alexAubin merged [pull request #9](https://github.com/YunoHost/appgenerator/pull/9): More fixes
[20:25:32]
<Yunohost Git/Infra notifications> [appgenerator] alexAubin pushed 8 commits to main ([1cb731f845d6...153bba5fdabf](https://github.com/YunoHost/appgenerator/compare/1cb731f845d6...153bba5fdabf))
[20:25:33]
<Yunohost Git/Infra notifications> [appgenerator/main] Update restore.j2 - Éric Gaspar
[20:25:34]
<Yunohost Git/Infra notifications> [appgenerator/main] reinstall node - Éric Gaspar
[20:25:35]
<Yunohost Git/Infra notifications> [appgenerator/main] Merge pull request #9 from ericgaspar/main More fixes - Alexandre Aubin
[21:10:08]
<Aleks (he/him/il/lui)> ci-apps-dev is slow af @_@
[21:50:03]
<Carlos Solís> > <@ghose:tchncs.de> yes, try **appgenerator**, at least you get basic strucuture for the package.
Thanks, now I have a template for the system. Now the next steps I need to check are:
- Making sure I can install for both x86 and ARM
- Adding a systemd file to the installation steps
- Running the downloaded executable in order to generate a VAPID and append it to the systemd file
[22:09:13]
<thomas> Hi all,
I'm currently working on Mitra, an ActivityPub microblogging server. The server app is built during the install. Does this mean that it could be supported by architectures other than amd64?
[22:49:11]
<orhtej2> > <thomas> Hi all,
> I'm currently working on Mitra, an ActivityPub microblogging server. The server app is built during the install. Does this mean that it could be supported by architectures other than amd64?
mitra is already packaged? https://github.com/YunoHost-Apps/mitra_ynh
[22:52:45]
<thomas> Yup, I did that 🤪
[23:00:22]
<thomas> Just wondering how I could manage to put architectures = "all" in manifest.toml
[23:02:39]
<Aleks (he/him/il/lui)> by ugh .... editing the line ? 😶🌫️ 🙈
[23:08:45]
<thomas> Great idea, but I'll save it for the moment I'm sure it does nicely install on other architectures than amd64. When I began working on the package, I was planning to use a .deb file provided on the upstream repo. But then someone here told me that a build during the install would allow to have the app installed on other architectures.
[23:09:24]
<thomas> So now thepackage runs a cargo build during the install and seems to work great (at least on my server where I tested it)
[23:09:36]
<thomas> But I haven't tested it on other architectures.
[23:11:07]
<thomas> Also the cargo build is for the backend, but there's also a frontend built with nodejs. So I'm wondering if it's the same or not: can I use a pre-built archive (as it is now in the master branch), or would it be better to also build the frontend during the install.
[23:12:11]
<orhtej2> > <thomas> But I haven't tested it on other architectures.
Should be architecture agnostic, but if the project releases oftec consider preferring to ship binaries
[23:12:54]
<Aleks (he/him/il/lui)> >a build during the install would allow to have the app installed on other architectures.
[23:12:56]
<Aleks (he/him/il/lui)> 🤔
[23:13:00]
<Aleks (he/him/il/lui)> who said that 👀
[23:13:23]
<Aleks (he/him/il/lui)> if the .deb is provided for all the target architecture it's not a problem to use .debs
[23:14:30]
<thomas> Oh, no, its a amd64 deb, actually (see here: https://codeberg.org/silverpill/mitra/releases/tag/v3.9.0)
[23:14:50]
<thomas> (As of who told me that, I don't remeber, was a few weeks ago)
[23:30:17]
<thomas> Anyhow, I'd just like to know if the nodejs pre-built tarball can safely be used as is on any architecture or if a specific build is preferable for each one.
[23:32:27]
<orhtej2> > <thomas> Anyhow, I'd just like to know if the nodejs pre-built tarball can safely be used as is on any architecture or if a specific build is preferable for each one.
It's likely to be specific to arch unless that's a bunch of static assets
[23:32:48]
<orhtej2> Is it served by 'naked' nginx?
[23:37:27]
<orhtej2> > Is it served by 'naked' nginx?
Answering myself
`This will produce a static website in the /dist directory.`
so you're good shiping prebuilt for all archs
[23:37:57]
<orhtej2> Problem is it hardcodes uris x_x
[23:40:08]
<thomas> Any chance you could elaborate on this? If I get what it's about I might ask the upstream developer to work on it