[00:22:15]
<m606> > In the change_url context, variables called new_domain, new_path, old_domain, old_path will be available, as well as change_domain and change_path equal to 0 (false) or 1 (true) depending if the domain / path changed
https://doc.yunohost.org/packaging/scripts/#variables-available-in-a-script-context
Can I find something similar in `restore` script ? For the case where admin backups an app on a Yunohost instance with domain1.tld and then restore the app on another YNH instance on domain2.tld.
[00:26:53]
<Aleks (he/him/il/lui)> restoration always happen on the same domain the app was installed on
[00:49:48]
<m606> Ok thanks. What happens if someone lose access to his/her domain name?
And if then his/her servers crashes - cannot restore until recovered the original domain name?
[00:51:51]
<Aleks (he/him/il/lui)> you can always add the domain to yunohost even if you don't own it, e.g. you can add google.com as a domain on your yunohost if you want
[00:51:57]
<Aleks (he/him/il/lui)> and then tweak /etc/hosts
[00:52:53]
<Aleks (he/him/il/lui)> but yeah sure, would be nice to be able to restore on another domain, and also using a different app_id (eg you can't restore an app named `wordpress__2` if there's already a `wordpress__2` on the new server, which feels stupid but is actually not trivial to solve)
[01:18:27]
<m606> Or do that and then run `change_url` manually I guess (that way change_url script will get correct content for vars `$old_domain` & `$old_path`)?
[02:08:09]
<Aleks (he/him/il/lui)> yes
[05:58:33]
<Yunohost Git/Infra notifications> [apps] ericgaspar pushed 1 commit to update_app_levels: Update apps.toml ([3663f410](https://github.com/YunoHost/apps/commit/3663f4101fc0b2f2fd5d19345c3008dcd0014abf))
[05:58:38]
<Yunohost Git/Infra notifications> [apps] ericgaspar edited [pull request #3037](https://github.com/YunoHost/apps/pull/3037): Update app levels according to CI results
[05:59:26]
<Yunohost Git/Infra notifications> [apps] ericgaspar pushed 1 commit to update_app_levels: Update apps.toml ([6943bd62](https://github.com/YunoHost/apps/commit/6943bd62f1068c2a53434f405dce5b3ba5222513))
[05:59:32]
<Yunohost Git/Infra notifications> [apps] ericgaspar edited [pull request #3037](https://github.com/YunoHost/apps/pull/3037): Update app levels according to CI results
[05:59:33]
<Yunohost Git/Infra notifications> [apps] ericgaspar edited [pull request #3037](https://github.com/YunoHost/apps/pull/3037): Update app levels according to CI results
[05:59:37]
<Yunohost Git/Infra notifications> [apps] ericgaspar merged [pull request #3037](https://github.com/YunoHost/apps/pull/3037): Update app levels according to CI results
[05:59:37]
<Yunohost Git/Infra notifications> [apps] ericgaspar pushed 1 commit to main: Update app levels according to CI results (#3037) * Update app levels according to CI results * :art: Format TOML with... ([c5cdb9bf](https://github.com/YunoHost/apps/commit/c5cdb9bf475959331bae7774e51ef2adea231e4b))
[05:59:38]
<Yunohost Git/Infra notifications> [apps] ericgaspar deleted branch update_app_levels
[06:33:18]
<Yunohost Git/Infra notifications> [mastodon_ynh] Tagadda pushed 1 commit to master: Update manifest.toml ([70e2e0da](https://github.com/YunoHost-Apps/mastodon_ynh/commit/70e2e0da5696b84ee599fd78c2ebfbfedec83d5d))
[09:03:55]
<Yunohost Git/Infra notifications> [apps] Josue-T [commented](https://github.com/YunoHost/apps/pull/3037#issuecomment-3041227121) on [issue #3037](https://github.com/YunoHost/apps/pull/3037) Update app levels according to CI results: Hello, It seem that for some apps there are a level issue since some week. By example seafile is marked as broken even ...
[09:59:46]
<Yunohost Git/Infra notifications> [apps] orhtej2 [commented](https://github.com/YunoHost/apps/pull/3037#issuecomment-3041269041) on [issue #3037](https://github.com/YunoHost/apps/pull/3037) Update app levels according to CI results: The proper CI is struggling to get past backp tests where the archive is big, and so is the case for seafile: https:...
[13:11:20]
<florent[m]> miro5001 (and maybe Aleks (he/him/il/lui)) you seemed to be interested in my work on cryptroot-unlock, here is the package:
https://github.com/YunoHost-Apps/cryptroot-unlock_ynh
If you wish to review it, it could be very helpful.
I'll make a PR to add this app to the catalog a bit later.
[20:30:19]
<m606> Hello, regarding `[install.init_main_permission]`, to set by default the admin group the value would be `admins`, right?
[20:37:40]
<m606> nevermind, I will use `all_users` I guess eventually...
[20:37:57]
<Spok> not sure what you're trying to achieve
[20:38:35]
<Spok> https://github.com/YunoHost-Apps/agora_ynh/blob/2b24bff1d488ecdd8b86ce953e95e20a49f4ab00/manifest.toml#L42 <- this will issue a question who should be able to visit app - everyone, logged in users or admins only
[20:38:48]
<Spok> you want to set the value to hardcoded or something?
[20:41:50]
<m606> no just wanted to set `admins` by default but was wondering whether that was the correct value to do so. But thanks your comment reminded me indeed that there was a list of answers - so yes it is `admins`.
[22:20:09]
<Yunohost Git/Infra notifications> [apps_tools] oleole39 opened [pull request #36](https://github.com/YunoHost/apps_tools/pull/36): Fix READMEs broken by GitHubs styling update
[22:21:56]
<Yunohost Git/Infra notifications> [piped_ynh] yunohost-bot opened [pull request #216](https://github.com/YunoHost-Apps/piped_ynh/pull/216): Upgrade sources
[22:29:11]
<Yunohost Git/Infra notifications> Autoupdater just ran, here are the results:
- 40 pending update PRs
- 29 new apps PRs
- 6 failed apps updates: autobd, homebox, khatru-pyramid, omeka-s, prestashop, teddit
See the full log here: https://paste.yunohost.org/raw/ledavarixo
Autoupdate dashboard: https://apps.yunohost.org/dash?filter=autoupdate
[22:52:57]
<trendless> I've been poking at Sharkey and I think I've got fresh installs working again using a release rather than cloning the repo (though only v4.2 -- it looks like there have been some dependency changes in 4.3 that still aren't playing nice).
I've not done a ynh PR before, happy to make one if it won't introduce issues for folks who already have a working v4.2 install.