Monday, June 12, 2023
apps@conference.yunohost.org
June
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
   
             

[03:03:33] <Yunohost Git/Infra notifications> App lstu rises from level 6 to 8 in job [#16342](https://ci-apps.yunohost.org/ci/job/16342) !
[07:13:42] <Yunohost Git/Infra notifications> App horde stays at level 4 in job [#16349](https://ci-apps.yunohost.org/ci/job/16349)
[07:27:54] <lapineige> Does someone have any idea about how to fix this ? 😅
https://github.com/YunoHost-Apps/wallabag2_ynh/pull/168#issuecomment-1586736622
[10:26:09] <Yunohost Git/Infra notifications> [nextcloud_ynh] @ericgaspar pushed 1 commit to v2_PostgreSQL: Update restore ([9902ad32](https://github.com/YunoHost-Apps/nextcloud_ynh/commit/9902ad326e853537d350a877e02399c52a5c41bc))
[10:26:13] <Yunohost Git/Infra notifications> [nextcloud_ynh] @ericgaspar pushed 1 commit to v2_PostgreSQL: cleaning ([59f4d751](https://github.com/YunoHost-Apps/nextcloud_ynh/commit/59f4d751efc1fb4ff6cefd1ce2811dc3280c5436))
[10:26:15] <Yunohost Git/Infra notifications> [nextcloud_ynh] @ericgaspar pushed 1 commit to v2_PostgreSQL: Update _common.sh ([931a3bc5](https://github.com/YunoHost-Apps/nextcloud_ynh/commit/931a3bc507609f24113d7d955dba655ea91aae78))
[10:26:21] <Yunohost Git/Infra notifications> [nextcloud_ynh/v2_PostgreSQL] Update upgrade - Éric Gaspar
[10:26:21] <Yunohost Git/Infra notifications> [nextcloud_ynh] @yunohost-bot pushed 1 commit to v2_PostgreSQL: Auto-update README ([0addb2ad](https://github.com/YunoHost-Apps/nextcloud_ynh/commit/0addb2ad955ef70363e47e1f36aab88196b1e297))
[10:26:21] <Yunohost Git/Infra notifications> [nextcloud_ynh/v2_PostgreSQL] Auto-update README - yunohost-bot
[10:26:21] <Yunohost Git/Infra notifications> [nextcloud_ynh] @ericgaspar [commented](https://github.com/YunoHost-Apps/nextcloud_ynh/pull/581#issuecomment-1586964341) on [issue #581](https://github.com/YunoHost-Apps/nextcloud_ynh/pull/581) Packaging version 2 PostgreSQL: testme
[10:26:21] <Yunohost Git/Infra notifications> [nextcloud_ynh] @yunohost-bot [commented](https://github.com/YunoHost-Apps/nextcloud_ynh/pull/581#issuecomment-1586964395) on [issue #581](https://github.com/YunoHost-Apps/nextcloud_ynh/pull/581) Packaging version 2 PostgreSQL: Fingers crossed
[[Test Badge](https://img.shields.io/endpoint?url=https://ci-apps-dev.yunohost.org/ci/api/job/7732/bad...
[10:26:21] <Yunohost Git/Infra notifications> [nextcloud_ynh] @ericgaspar pushed 7 commits to v2_PostgreSQL ([931a3bc50760...884f530a1cfe](https://github.com/YunoHost-Apps/nextcloud_ynh/compare/931a3bc50760...884f530a1cfe))
[10:26:21] <Yunohost Git/Infra notifications> [nextcloud_ynh/v2_PostgreSQL] Update manifest.json - Éric Gaspar
[10:26:21] <Yunohost Git/Infra notifications> [nextcloud_ynh/v2_PostgreSQL] Merge branch testing into v2_PostgreSQL - Éric Gaspar
[10:26:22] <Yunohost Git/Infra notifications> [nextcloud_ynh/v2_PostgreSQL] Update install - Éric Gaspar
[10:26:22] <Yunohost Git/Infra notifications> [nextcloud_ynh] @ericgaspar pushed 3 commits to v2_PostgreSQL ([0addb2ad955e...03f52ae739c3](https://github.com/YunoHost-Apps/nextcloud_ynh/compare/0addb2ad955e...03f52ae739c3))
[10:26:22] <Yunohost Git/Infra notifications> [nextcloud_ynh/v2_PostgreSQL] Merge branch v2_PostgreSQL of https://github.com/YunoHost-Apps/nextcloud_ynh into v2_PostgreSQL - Éric Gaspar
[10:26:23] <Yunohost Git/Infra notifications> [nextcloud_ynh] @ericgaspar pushed 1 commit to v2_PostgreSQL: fix ([33d901ce](https://github.com/YunoHost-Apps/nextcloud_ynh/commit/33d901ce3a740847dfeb5cb0d429b3cd358bb918))
[11:17:10] <Yunohost Git/Infra notifications> [nextcloud_ynh] @ericgaspar pushed 7 commits to v2 ([dce54d8f45cb...2a20ec1f54b7](https://github.com/YunoHost-Apps/nextcloud_ynh/compare/dce54d8f45cb...2a20ec1f54b7))
[11:17:12] <Yunohost Git/Infra notifications> [nextcloud_ynh] @yunohost-bot pushed 1 commit to v2: Auto-update README ([2d88325a](https://github.com/YunoHost-Apps/nextcloud_ynh/commit/2d88325ab6bfe3ec5fda545175346891a6e73f37))
[11:17:14] <Yunohost Git/Infra notifications> [nextcloud_ynh/v2] Update manifest.json - Éric Gaspar
[11:17:17] <Yunohost Git/Infra notifications> [nextcloud_ynh/v2] Auto-update README - yunohost-bot
[11:17:54] <Yunohost Git/Infra notifications> [nextcloud_ynh/v2] Merge branch testing into v2 - Éric Gaspar
[12:28:01] <lapineige> Do you know if it's possible in app packaging to provide multiple ports instead of the only one given by `[resources.ports]` ?
[12:31:25] <eric_G> https://yunohost.org/fr/packaging_apps_resources#ports
[15:31:30] <eric_G> why are we not updating Nextclouds apps in upgrade script with `exec_occ app:update --all`?
[15:33:06] <Aleks (he/him/il/lui)> (or auto-disabling the apps ? i thought it was the case at some point, but i'm not following closely what's happening on Nextcloud ...)
[15:34:28] <eric_G> the strange thing is that we are desabling the app mail: https://github.com/YunoHost-Apps/nextcloud_ynh/blob/caf917f3d8a2f2a3a4b7cd3d62f43fa3c4ddddc3/scripts/upgrade#L269-L272
[15:34:41] <eric_G> so we shouldn't get this issue https://forum.yunohost.org/t/solved-resolu-erreur-lors-de-la-maj-de-nextcloud-error-when-updating-nextcloud-24-0-7-26-0-2/25104
[15:36:55] <Aleks (he/him/il/lui)> hmm, could it be that maybe the grep doesnt catch it for some reason ?
[15:37:49] <Aleks (he/him/il/lui)> we should ask for the full output of `app:list`
[15:37:56] <Aleks (he/him/il/lui)> (or try on an existing setup)
[15:38:01] <Aleks (he/him/il/lui)> maybe the data format changed somehow
[15:38:56] <lapineige> > <@ericg:matrix.org> why are we not updating Nextclouds apps in upgrade script with `exec_occ app:update --all`?

could it be that if one upgrade fails for some reasons that would fail the whole operation ?
[15:39:16] <lapineige> It was the case, but it was also quite painful as users 😅 (you would have to remember the complete list and active them again one by one (and it takes time for each single one))
[15:55:37] <Yunohost Git/Infra notifications> [nextcloud_ynh] @ericgaspar pushed 1 commit to v2: update apps during upgrade ([c80b08ab](https://github.com/YunoHost-Apps/nextcloud_ynh/commit/c80b08ab36cfe6652a432df6cf16e5a80ac1f529))
[15:57:30] <Aleks (he/him/il/lui)> ideally it would be nice to have a "dry-run" check of which apps can be upgraded, or rather are there any apps which can't be upgraded and must be manually disabled before running the upgrade
[15:58:13] <Aleks (he/him/il/lui)> maybe there's something in the nextcloud CLI for this but i really don't know much about it
[15:59:20] <eric_G> does an app get updated if it's disable?
[16:00:32] <eric_G> I don't know much either
[16:03:34] <Aleks (he/him/il/lui)> btw (unrelate) I was thinking these days that we could have some sort of "setting" resource to define custom/additional settings which would be provisioned with a default value, instead of creating them in the install script, and having to handle the recurring annoying `if [[ -z ${foobar:-} ]]; then init the variable + set the setting` in the upgrade script
[16:06:20] <eric_G> > "setting" resource

What do you mean by setting resource?
[16:07:34] <Aleks (he/him/il/lui)> something like

```
[resource.settings]
fpm_usage.default = "low"
fpm_footprint.default = "50"
```

(i never remember which are the relevant values for these, this is just an example)
[16:07:53] <Aleks (he/him/il/lui)> and also some way to initialize them from code like uuuuu
[16:08:26] <Aleks (he/him/il/lui)> `email.default.from_bash = "ynh_get_user_info $admin key=email"`

[16:08:28] <Aleks (he/him/il/lui)> idk
[16:09:34] <Aleks (he/him/il/lui)> or actually no need for a special syntax between literals and dynamic, we can just assume everything is bash maybe
[16:10:19] <Aleks (he/him/il/lui)> or `foobar.default = "$(some command)"`, idk
[16:10:21] <Aleks (he/him/il/lui)> 🤔
[16:10:21] <Aleks (he/him/il/lui)> (thinking out loud)
[16:13:00] <Aleks (he/him/il/lui)> anyway, just throwing this in the wild in case somebody is interested ;P I think i'll focus on reviewing/merging PRs which can easily be merged and trying to bootstrap the app CI campaign for bookworm
[16:13:02] <eric_G> a kind of `manifest.toml` that rule them all 😅
[16:15:49] <eric_G> I think that make sens for the fpm_usage/footprint stuff
[16:17:16] <eric_G> I just got bored of adding this do I just set `ynh_add_fpm_config --usage=low --footprint=low`
[16:17:17] <eric_G> *so
[16:18:10] <Aleks (he/him/il/lui)> yeah i was thinking it's cumbersome when reading https://github.com/YunoHost/example_ynh/pull/208 the other day
[16:18:41] <Aleks (he/him/il/lui)> but for this specific case maybe just tweaking the helper behavior would be enough
[16:19:24] <Aleks (he/him/il/lui)> like the `--usage`/`--footprint` could just be the default value to initialize the `fpm_usage`/`fpm_footprint` behind the scene, but use the current setting value if the setting already exists (dunno if that's clear)
[16:19:42] <Aleks (he/him/il/lui)> this way the packager would not have to care anymore about the fpm_usage/fpm_footprint setting ...
[16:41:10] <tituspijean[m]> Around the time the config panels were implemented I remember suggesting having `[core.php]` or whatever string that would automatically be replaced by the cumbersome always-copy-pasted php lines.

I totally get behind your suggestion of doing that as early as the manifest 😁
[16:48:28] <Aleks (he/him/il/lui)> ah yes but that's for config panel
[16:48:36] <Aleks (he/him/il/lui)> the [core.php] thing
[16:49:11] <Aleks (he/him/il/lui)> like to standardize the interface to tweak the fpm usage etc, but here it's more about a general thing about settings
[16:49:41] <Aleks (he/him/il/lui)> but yeah we also have to be careful about the way we should design such a `[resource.settings]` to try to mitigate the mess / redundancy with the config panel
[16:51:35] <Aleks (he/him/il/lui)> e.g. https://github.com/YunoHost/issues/issues/1973
[21:35:39] <Yunohost Git/Infra notifications> App pixelfed rises from level 4 to 8 in job [#16367](https://ci-apps.yunohost.org/ci/job/16367) !
[22:27:52] <tituspijean[m]> If one chooses not to have a database for a my_webapp, then the post_install message might be very confusing:
[22:27:56] <tituspijean[m]> https://aria.im/_matrix/media/v1/download/pijean.ovh/c217184df93bec90467c438e6ac894fecff63964d3e59128a04c75fc3e7c19aa
[22:28:43] <tituspijean[m]> (eh... it's written "*if you have asked for a database*"... nevermind 🙂 )
[22:33:03] <lapineige> (That's still confusing for many users)