[03:50:55]
<Yunohost Git/Infra notifications> [cloud-init-images] p4p4j0hn opened [issue #1](https://github.com/YunoHost/cloud-init-images/issues/1): Feature Request: Create other image types
[08:01:39]
<Yunohost Git/Infra notifications> [issues] m4lvin [commented](https://github.com/YunoHost/issues/issues/2494#issuecomment-2594767241) on [issue #2494](https://github.com/YunoHost/issues/issues/2494) Authentication form does not accept Bitwardens credentials: I can confirm this, and it is not bitwarden specific as I use https://codeberg.org/PassFF/passff It does manage to fill...
[08:07:50]
<Yunohost Git/Infra notifications> [issues] nicofrand edited [issue #2494](https://github.com/YunoHost/issues/issues/2494): Authentication form does not accept password managers credentials
[09:40:14]
<@chrichri:ween.de> orhtej2 in support:
> I'm confused why are you not fixing venv from app shell where you would be the proper user already. But yes, you can chown the files, they should be owned by the app
That is something I have been wondering about already: Wouldn't it be better if files that an app does not need to change (and which are possibly executable also) would be owned by a different user than the webserver or the app to protect those files from being altered?
[11:57:14]
<Salamandar> > <@chrichri:ween.de> orhtej2 in support:
> > I'm confused why are you not fixing venv from app shell where you would be the proper user already. But yes, you can chown the files, they should be owned by the app
>
> That is something I have been wondering about already: Wouldn't it be better if files that an app does not need to change (and which are possibly executable also) would be owned by a different user than the webserver or the app to protect those files from being altered?
Chmod -w does the trick ;)
[16:28:23]
<Aleks (he/him/il/lui)> https://github.com/YunoHost/yunohost/blob/dev/helpers/helpers.v2.1.d/nodejs#L68-L88 my god what are we even doing here ... tweaking $PATH and mv-ing some binary just to ... do a cp and a search and replace ? x_x
[18:03:34]
<Aleks (he/him/il/lui)> why 👏 do we need 👏 xxenv-latest 👏 ffs
[18:14:33]
<Salamandar> translate 3.0 to "latest of the 3.0.x series"
[18:16:46]
<Aleks (he/him/il/lui)> Zmlerf oké @_@
[18:21:06]
<Aleks (he/him/il/lui)> The readme of xxenv seems to suggest this is only the case if we call 'fooenv latest install x.y' instead of 'fooenv install x.y' though ?
[18:26:09]
<Salamandar> yes but we directly call it iirc
[18:32:20]
<Aleks (he/him/il/lui)> without xxenv-latest :
```
root@yolo:~/goenv# bin/goenv install 1.20
Using latest patch version 1.20.14
```
[18:32:25]
<Aleks (he/him/il/lui)> ¯\_(ツ)_/¯
[18:32:31]
<Aleks (he/him/il/lui)> i'd say let's trash xxenv-latest ...