Wednesday, April 15, 2026
apps@conference.yunohost.org
April
Mon Tue Wed Thu Fri Sat Sun
    1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17 18 19
20 21
22
23 24 25 26
27 28 29 30      
             

[00:31:38] <Yunohost Git/Infra notifications> Autoupdater just ran, here are the results:

- 62 pending update PRs
- 2 failed apps updates: loki, passed

See the full log here: https://paste.yunohost.org/raw/ihunohihur
Autoupdate dashboard: https://apps.yunohost.org/dash?filter=autoupdate
[00:31:40] <m606> https://github.com/YunoHost/doc/pull/2758
[00:35:46] <Yunohost Git/Infra notifications> App lichenmarkdown failed all tests in job [#30946](https://ci-apps.yunohost.org/ci/job/30946) !
[00:53:13] <Yunohost Git/Infra notifications> App filegator failed all tests in job [#30949](https://ci-apps.yunohost.org/ci/job/30949) !
[06:25:27] <Yunohost Git/Infra notifications> App lichenmarkdown failed all tests in job [#30946](https://ci-apps.yunohost.org/ci/job/30946) !
[06:28:15] <Yunohost Git/Infra notifications> App openproject failed all tests in job [#30877](https://ci-apps.yunohost.org/ci/job/30877) !
[10:18:10] <Yunohost Git/Infra notifications> [nextcloud_ynh] D​avidLep0le [commented](https://github.com/YunoHost-Apps/nextcloud_ynh/issues/871#issuecomment-4251187238) on [issue #871](https://github.com/YunoHost-Apps/nextcloud_ynh/issues/871) One more break in the nextcloud yunohost app...: > YNH is not responsible for app (in)compatibility with the latest nextcloud releases.

Hello,
i know the ynh team is al...
[11:03:07] <Jochen> Hi. I created my first Pull-Request. This is for Rspamd. Can someone please review this?
https://github.com/YunoHost-Apps/rspamd_ynh/pull/33
[11:48:36] <miro5001> That's a massive PR. Did you manually test it on both bookworm and Trixie?
[11:51:38] <miro5001> And I suppose there should be a force upgrade that needs to be run when someone installs it on bookworm then migrates to Trixie
[11:57:58] <Jochen> I only tested it with Trixie.

Do you have experience with rspamd?
[12:02:09] <miro5001> Sorry, at all.
I feel like spammers didn't get my emails 🙏
[12:14:55] <orhtej2> > <@jstiepel:matrix.org> I only tested it with Trixie.
>
> Do you have experience with rspamd?

There's a maintainer for this project, right?
[12:14:58] <orhtej2> Lol no
[12:14:59] <David> Hi folks 👋🏻
[12:21:09] <Thomas> It's perfectly fine, that's the way most app works
[12:21:09] <David> I'm working on packaging an app for Yunohost and could use a bit of advice. The app requires a bunch of env vars and setting them through the system unit file seems like the way to go. Is using the `EnvironmentFile` directive suitable? If so, would putting that file in the app install directory be appropriate or should it live somewhere in `/etc/` ?
[12:21:25] <Thomas> You can put the env file in the $install_dir
[12:39:00] <David> fantastic, thanks
[13:17:16] <m606> i have a python app which loads fine, apart from the static files (JS+CSS) which are not loaded (despite showing a 200 response code) with:
- a basic nginx.conf
```
location / {
include proxy_params_no_auth;
proxy_pass http://127.0.0.1:__PORT__;
try_files $uri $uri/ /index.html;
}
```
- files owned by $app:$app except for files and folders living in `$install_dir/arm/ui/static` and folder up to there (to allow traversal) with $app:www-data.

Still console says those files are blocked due to incorrect MIME type ('text/html').
[13:18:01] <m606> adding this to nginx.conf doesn't help
```
location /static/ {
alias __INSTALL_DIR__/arm/ui/static/;
expires 30d;
}
```
[14:34:26] <miro5001> Try root instead of alias
[14:48:50] <m606> no luck
[14:49:36] <m606> but adding the static location snippet (whether alias or root) gives a response code for the assets of 404
[14:49:46] <m606> (compared to 200 without the snippet)
[14:54:57] <otm33> and removing `try_files $uri $uri/ /index.html;` ?
[14:56:29] <m606> ah yes that was it!! thanks.
I don't understand why though!
[14:57:22] <m606> (it doesn't even need the static snippet)
[15:02:32] <otm33> m606: I think that whan you proxy_pass there is no need to specify try_files but I don’t understand why proxy_pass didn’t take precedence over try_files in the block.
[15:11:14] <m606> hmm, and would using `try_files` at root and `proxy_pass` at a named location like follows be safer? https://nginx.org/en/docs/http/ngx_http_core_module.html#:\~:text=Example%20in%20proxying%20Mongrel:
[15:12:30] <m606> hmm no I guess it doesn't change anything safety-wise
[15:13:03] <m606> this is more like "search for local file and if not go to proxy"
[15:13:19] <m606> I don't need that here I believe
[15:13:48] <m606> thanks that little line was blocking me for quite some time already!
[15:17:01] <otm33> just curious : what happens if you only remove the /index.html fallback from try_files?
[15:26:47] <m606> you mean`try_files $uri $uri/` ?
[15:27:41] <m606> error 500
[15:28:28] <miro5001> try_files looks for files.
[16:43:50] <m606> from above linked example from nginx doc, to so so you need to have `try_files $uri $uri/ @myproxy` and having defined @myproxy location containing the `proxy_pass` instruction
[17:05:28] <otm33> yes, they seem to act as independent pipelines, if try\_files returns an error (and does not point to other location) proxy\_pass is not tried.
[19:04:38] <otm33> Can someone explain why some apps include in their restore script both `ynh_restore "/etc/php/$php_version/fpm/pool.d/$app.conf"` and `ynh_config_add_phpfpm` ? At this point I can't get it
[19:04:43] <orhtej2> > <@otm33:matrix.org> Can someone explain why some apps include in their restore script both `ynh_restore "/etc/php/$php_version/fpm/pool.d/$app.conf"` and `ynh_config_add_phpfpm` ? At this point I can't get it

Restore seems the right approach
[19:04:48] <otm33> Thanks. If a php restart is needed, `ynh_restore "/etc/php/$php_version/fpm/pool.d/$app.conf"` and `ynh_systemctl --service=php$php_version-fpm --action=reload` should be sufficient, right ?
[21:43:42] <Yunohost Git/Infra notifications> [apps] y​unohost-bot opened [pull request #3431](https://github.com/YunoHost/apps/pull/3431): Add Reitti to wishlist
[22:24:21] <Yunohost Git/Infra notifications> [mastodon_ynh] y​unohost-bot opened [pull request #561](https://github.com/YunoHost-Apps/mastodon_ynh/pull/561): Upgrade to v4.5.9
[22:28:00] <otm33> cd ..
[22:29:01] <Yunohost Git/Infra notifications> Autoupdater just ran, here are the results:

- 42 pending update PRs
- 19 new apps PRs: atuin, commafeed, element-call, esphome, indico, invoiceninja5, jackett, jellyseerr, liberaforms, mastodon, n8n, nocodb, nodebb, syncserver-rs, tandoor, tooljet, wekan, wger, whitebophir
- 2 failed apps updates: loki, passed

See the full log here: https://paste.yunohost.org/raw/viwafugevu
Autoupdate dashboard: https://apps.yunohost.org/dash?filter=autoupdate