[00:28:08]
<m606> > <@augierle42e:matrix.org> Well, in the simplest scenario, you can install the admin in a virtualenv, spawn it on a different port than the prod admin, copy the Nginx configuration so it is exposed on a different path, then edit the files using nano or vi and restart by hand upon modification
thanks for the clues. I found the web admin path at `usr/share/yunohost/admin/` but indeed minified.
I don't know yet how I could change just a file - say `SystemUpdate-{string}.js` from a more readable dev version (the file I want to modify and test is https://github.com/YunoHost/yunohost-admin/blob/ab13e6e659a191a7d7bb69d1d351093e11e4ac87/app/src/views/update/SystemUpdate.vue).
Nothing too obvious spontaneously for me with the PyCharm trick, I would need to dig it further.
[09:50:46]
<Aleks (he/him/il/lui)> I dont think there's anything straightforward/magic to edit the webadmin code in-place, the way we usually dev on the core etc. is with the ynh-dev script, more precisely ./ynh-dev use-git yunohost-admin (inside an existing yunohost setup such as a dev LXC), it installs the npm dependencies and rebuilds the webadmin from source
[09:51:18]
<Aleks (he/him/il/lui)> I dont think there's anything straightforward/magic to edit the webadmin code in-place, the way we usually dev on the core etc. is with the ynh-dev script, more precisely for the webadmin : ./ynh-dev use-git yunohost-admin (inside an existing yunohost setup such as a dev LXC), it installs the npm dependencies and rebuilds the webadmin from source
[12:45:37]
<Aleks (he/him/il/lui)> hmmm i would think 10G~20G should be enough, how much do you have ?
[12:45:44]
<Aleks (he/him/il/lui)> NB : you shouldnt have to build the image yourself, we already have pre-built images
but maybe you meant installing incus itself and succesfully launching a container (that's usually the most painful part, typically there's no network inside the container because of DHCP shenanigans)
[13:06:47]
<m606> > <@Alekswag:matrix.org> NB : you shouldnt have to build the image yourself, we already have pre-built images
> but maybe you meant installing incus itself and succesfully launching a container (that's usually the most painful part, typically there's no network inside the container because of DHCP shenanigans)
ok that what I was afraid of, currently finding more than ~4G free will be annoying. I will do something to change this but it will take some time.
Indeed I meant installing incus itself, as if I remember well before it was using Canonical LXD which (when I had tried back then to install ynh-dev) could be installed only via snap or built from source and I had tried the latter without success.
I actually would like to address this rather simple issue https://github.com/YunoHost/issues/issues/2072 and thought I could manage without ynh-dev, but I am now afraid that finding a workaround could be even more complex than crafting that PR... 🫠 I'll wait till I have disk space.
[13:08:29]
<Aleks (he/him/il/lui)> (but yeah ideally we would have sandbox machines on our infra x_x)
[13:08:29]
<Aleks (he/him/il/lui)> alternatively you can also setup a VPS somewhere to use as a dev machine, like installing yunohost with the classic curl|bash and then setting up ynh-dev inside it
[13:15:30]
<m606> > <@Alekswag:matrix.org> (but yeah ideally we would have sandbox machines on our infra x_x)
that would be nice, but it sounds to account for quite much of work that would benefit a limited number of people generally able to set up their own dev environment (I guess disk space issues like mine are not that frequent).
[13:18:05]
<Aleks (he/him/il/lui)> hmmmyeah but maintaining a working dev env sometime is hell, or for example right now i have one to work on packaging v3 but since it's unstable I can't really test apps on it (+ I have limited RAM / disk space too), and if it were semi-public it would be easier to demo / share pending work with other folks
[13:18:23]
<Aleks (he/him/il/lui)> and also for apps debugging when something funky happens and can't easily be debugged on CI
[13:18:52]
<Aleks (he/him/il/lui)> (I've heard horror stories about app packagers testing apps on their own prod servers 🙀)
[13:20:15]
<Aleks (he/him/il/lui)> anyway that's just a yakafokon
[13:22:13]
<m606> > <@Alekswag:matrix.org> and also for apps debugging when something funky happens and can't easily be debugged on CI
yes that would great to be able to freeze the CI at some point and be able to access the filesystem to debug!
[13:27:46]
<m606> > <@Alekswag:matrix.org> (I've heard horror stories about app packagers testing apps on their own prod servers 🙀)
oh that never happened to me! 🥴
[21:36:20]
<ljf> we have tried with optogram to use the tls sni feature, but it was strange SSL_ERROR_RX_RECORD_TOO_LONG (no certificate given in firefox)
https://paste.yunohost.org/raw/baxisesade
https://paste.yunohost.org/raw/muzidugoxa
https://paste.yunohost.org/raw/xoyunehawa
ynh 12.0.15
[21:41:30]
<Aleks (he/him/il/lui)> probably something to do with the proxy_protocol i would guess
[21:46:23]
<Aleks (he/him/il/lui)> maybe those notes from T ag can help idk : https://github.com/YunoHost/yunohost/pull/2105/files
[21:54:42]
<eric_G> > <@m606:matrix.org> oh that never happened to me! 🥴
Or to me 😅