[07:16:11]
<nemstudio18> > <@Alekswag:matrix.org> maybe the `$uri/` here https://github.com/YunoHost-Apps/299ko_ynh/blob/testing/conf/nginx.conf#L12 is problematic, idk, rough guess
In this case, the admin/ folder exists in /var/www/299ko/ and contains the necessary files for the CMS administration. The issue stems from the fact that the directive
try_files $uri $uri/ @__APP__;
detects the physical admin/ folder, which prevents requests from being passed to the front controller. This stops proper redirection to the admin interface.
To resolve this, you can add a specific configuration for the admin URL to force the rewrite. For example, insert the following lines before the general configuration:
location ^~ __PATH__/admin/ { try_files $uri $uri/ @__ADMIN__; } location @__ADMIN__ { rewrite ^__PATH__/admin/(.*)$ __PATH__/index.php?/$1 last; }
This configuration forces all requests to /admin to be routed to the CMS's index.php file, regardless of the physical existence of the admin/ folder.
After modifying the configuration, remember to reload Nginx:
sudo systemctl reload nginx
Then, test the admin access to verify that the issue is resolved.
I do not know if we can do whatever we want with the Nginx configuration file you are currently modifying. The solution proposed above comes from an AI, which has already surprised me in the past, so I thought I would propose it to you.
[07:31:23]
<Yunohost Git/Infra notifications> [synapse_ynh] centralscrutinizer21 opened [issue #518](https://github.com/YunoHost-Apps/synapse_ynh/issues/518): Upgrade from 1.123.0~ynh1 to 1.125.0~ynh1 fails
[07:31:45]
<Yunohost Git/Infra notifications> [synapse_ynh] centralscrutinizer21 edited [issue #518](https://github.com/YunoHost-Apps/synapse_ynh/issues/518): Upgrade from 1.123.0~ynh1 to 1.125.0~ynh1 fails
[07:32:02]
<Yunohost Git/Infra notifications> [synapse_ynh] centralscrutinizer21 edited [issue #518](https://github.com/YunoHost-Apps/synapse_ynh/issues/518): Upgrade from 1.123.0~ynh1 to 1.125.0~ynh1 fails
[09:06:32]
<nemstudio18> > <@nemstudio18:matrix.org> In this case, the admin/ folder exists in /var/www/299ko/ and contains the necessary files for the CMS administration. The issue stems from the fact that the directive
> try_files $uri $uri/ @__APP__;
> detects the physical admin/ folder, which prevents requests from being passed to the front controller. This stops proper redirection to the admin interface.
> To resolve this, you can add a specific configuration for the admin URL to force the rewrite. For example, insert the following lines before the general configuration:
> location ^~ __PATH__/admin/ { try_files $uri $uri/ @__ADMIN__; } location @__ADMIN__ { rewrite ^__PATH__/admin/(.*)$ __PATH__/index.php?/$1 last; }
> This configuration forces all requests to /admin to be routed to the CMS's index.php file, regardless of the physical existence of the admin/ folder.
> After modifying the configuration, remember to reload Nginx:
> sudo systemctl reload nginx
> Then, test the admin access to verify that the issue is resolved.
> I do not know if we can do whatever we want with the Nginx configuration file you are currently modifying. The solution proposed above comes from an AI, which has already surprised me in the past, so I thought I would propose it to you.
I just managed to install it with the administration, however I no longer have the themes, I think you have to force it like I did with admin/
[09:08:59]
<nemstudio18> > <@nemstudio18:matrix.org> In this case, the admin/ folder exists in /var/www/299ko/ and contains the necessary files for the CMS administration. The issue stems from the fact that the directive
> try_files $uri $uri/ @__APP__;
> detects the physical admin/ folder, which prevents requests from being passed to the front controller. This stops proper redirection to the admin interface.
> To resolve this, you can add a specific configuration for the admin URL to force the rewrite. For example, insert the following lines before the general configuration:
> location ^~ __PATH__/admin/ { try_files $uri $uri/ @__ADMIN__; } location @__ADMIN__ { rewrite ^__PATH__/admin/(.*)$ __PATH__/index.php?/$1 last; }
> This configuration forces all requests to /admin to be routed to the CMS's index.php file, regardless of the physical existence of the admin/ folder.
> After modifying the configuration, remember to reload Nginx:
> sudo systemctl reload nginx
> Then, test the admin access to verify that the issue is resolved.
> I do not know if we can do whatever we want with the Nginx configuration file you are currently modifying. The solution proposed above comes from an AI, which has already surprised me in the past, so I thought I would propose it to you.
https://github.com/NemStudio18/299ko_ynh/blob/master/conf%2Fnginx.conf#L1-L35
[09:14:28]
<nemstudio18> with this config I can access the admin but I no longer have a theme! maybe I have to force theme/ as admin/?
sorry, I'm trying things but I don't know anything about server configuration
[11:23:36]
<Yunohost Git/Infra notifications> [searxng_ynh] ewilly merged [pull request #377](https://github.com/YunoHost-Apps/searxng_ynh/pull/377): Upgrade to v2025.03.09
[11:23:41]
<Yunohost Git/Infra notifications> [searxng_ynh] ewilly deleted branch ci-auto-update-2025.03.09
[11:23:50]
<Yunohost Git/Infra notifications> [searxng_ynh] github-actions[bot] opened [pull request #378](https://github.com/YunoHost-Apps/searxng_ynh/pull/378): Upgrade master from testing
[11:24:02]
<Yunohost Git/Infra notifications> [searxng_ynh] ewilly merged [pull request #378](https://github.com/YunoHost-Apps/searxng_ynh/pull/378): Upgrade master from testing
[11:24:04]
<Yunohost Git/Infra notifications> [searxng_ynh] ewilly deleted branch master-promotion
[11:27:31]
<cippr> eric_G: Hello, master is merged into stable https://github.com/simplex-chat/simplexmq/commit/aa26a55df4c6fc39b4e7f5955dcdfa26d216d805
I'll do things tonight.
[11:50:57]
<nemstudio18> I'm not sure I understood the meaning of your message! Did you manage to make it work?
[12:00:32]
<eric_G> Yes, I did. No more 403 error on admin part 🎉
[12:02:16]
<nemstudio18> 😂
I'm relieved! I was afraid it came from 299ko! Hoping it finishes passing the tests! Do you think it will be marked as functional soon?😇
[12:02:47]
<nemstudio18> Anyway, congratulations on the quick work!
[12:08:38]
<eric_G> the app is queuing on the CI for validation and level https://ci-apps.yunohost.org/ci/
[12:13:05]
<eric_G> for the app update, is keeping `data` folder and replacing everything ok?
[12:14:13]
<nemstudio18> Oui exactement.
[12:14:17]
<nemstudio18> Yes !
[12:17:29]
<eric_G> (je suis français 😬)
[12:19:35]
<nemstudio18> Je m'en doutais mais on ne sait jamais ! pourrais tu m'expliquer vite fait ce qu'il va se passer après je comprends pas bien yunoruner cli stp ?
[12:20:57]
<eric_G> Après avoir été validée par la CI, l'app apparaît dans le catalogue et est disponible au monde.
[12:21:35]
<nemstudio18> Nikel merci ! Et pour les maj c'est automatique ? Quand nous chez 299ko il y a une maj ça se fait automatiquement ici?
[12:22:35]
<nemstudio18> (et la date dans le tableau s'est programmée hier CI ? Je comprends pas trop 😂 désolé je débute en même temps sur yunohost)
[12:26:00]
<eric_G> Lorsqu'une nouvelle mise à jour (avec un tag de version) est disponible upstream, nous devrions avoir une mise à jour automatique pour 299ko_ynh.
cf:
https://github.com/YunoHost-Apps/299ko_ynh/blob/140d1e5bca98419303fb831c897744f5ee803a80/manifest.toml#L56-L57
[12:29:27]
<eric_G> Si cette mise à jour réussit les tests de validation, elle doit être fusionnée manuellement dans Master.
Tu es peut-être intéressé par le maintien de cette app ? Je peux te rajouter comme mainteneur sur ce repo ?
[12:30:08]
<nemstudio18> Oui si tu veux tu peux mais je vais souvent t'appeler ^^
[12:30:16]
<eric_G> C'est facile, le plus gros est fait...
[12:32:30]
<nemstudio18> Ok bha pas de problème , surtout que j'aimerai mettre a jours une app que vous avez encore ! Bien que le projet d'origine ait été abandonné, un dev a maintenu et amélioré le système (après j'espère que vous n'avez rien contre un dev russe ...?) car il a fait un excellent taff sur fluxbb.
[12:33:01]
<eric_G> normalement tu as une invite
[12:34:17]
<nemstudio18> C'est bon bien reçu et validé ;) merci
[13:12:52]
<eric_G> Is it possible to achieve this password with 12 characters long and contain a digit, upper, lower and special characters with `ynh_string_random` helper?
[13:16:37]
<Aleks (he/him/il/lui)> \`passord="$(ynh\_string\_random)aA1#"` 😬
[13:16:43]
<Aleks (he/him/il/lui)> `passord="$(ynh\_string\_random)aA1#"` 😬
[13:16:50]
<Aleks (he/him/il/lui)> `passord="$(ynh_string_random)aA1#"` 😬
[13:28:30]
<eric_G> I found `password=$(tr -dc 'A-Za-z0-9!?%=' < /dev/urandom | head -c 12)`
[13:35:09]
<Aleks (he/him/il/lui)> yeah but the tricky part imho is that you have no guarantee that the randomly generated stuff contains all 4 flavors of chars
[13:35:38]
<Aleks (he/him/il/lui)> but you can increase the probability by increasing the length if it doesnt has to be exactly 12
[13:36:53]
<eric_G> increasing to 24
[14:48:38]
<miro5001> `openssl rand --base64 32 `
[14:48:49]
<miro5001> That's for Wiki.js?
[14:57:14]
<eric_G> yes
[15:00:38]
<Aleks (he/him/il/lui)> mandatory xkcd about passphrases :| https://imgs.xkcd.com/comics/password_strength_2x.png
[15:07:20]
<nemstudio18> eric_G: du coup les tests sont automatiquement fait dans une tranche horaire prévu c'est ça ? Et si ça passe le test (page que vous m'avez envoyée ou la page dash ? ) c'est a moi de fusionner dans le master du dépôt _ynh c'est ça ?
[15:20:03]
<orhtej2> > <@Alekswag:matrix.org> mandatory xkcd about passphrases :| https://imgs.xkcd.com/comics/password_strength_2x.png
These are trivial to break with hashcat and a wordlist 🙄
[15:21:09]
<Aleks (he/him/il/lui)> hashcat ?
[15:28:22]
<orhtej2> > <@Alekswag:matrix.org> hashcat ?
https://hashcat.net/hashcat/
[15:28:47]
<orhtej2> Gpu accelerated hash breaker basically
[15:30:00]
<Aleks (he/him/il/lui)> i dunno how passphrases can be faster to crack than "classic" passwords :| (ofc that depends on the actual length)
[15:31:33]
<orhtej2> Test
[15:31:33]
<orhtej2> > <@Alekswag:matrix.org> i dunno how passphrases can be faster to crack than "classic" passwords :| (ofc that depends on the actual length)
You can ask hashcat to use combinations of dictionary words rather than arbitrary strings, narrows down search space significantly
[15:32:46]
<Aleks (he/him/il/lui)> english words have somethings like 16 bits of entropy, characters have like 6 or 7 (and i'm pretty sure 90% people only have one caps and one special char just so that the password constrain is happy)
[15:33:38]
<Aleks (he/him/il/lui)> i mean my point is, an alphanumeric password with length = 24 is probably stronger than a alphanumeric+special char with length = 12
[15:33:47]
<Aleks (he/him/il/lui)> ¯\_(ツ)_/¯
[15:38:18]
<Aleks (he/him/il/lui)> (and requiring a special char is annoying because people may want to use long alphanumeric passwords, but having to add a special char in there fucks the memorization technique you may have around it etc)
[15:39:26]
<Aleks (he/him/il/lui)> > People tend to make stupid passwords, by forcing them to use capital letters, numbers and symbols, you force them to create better passwords than just their surname, 123 or their birthday.
@_@
[15:47:55]
<orhtej2> https://aria.im/_bifrost/v1/media/download/AZjWnE4Ff62W3VCEDcixFGUp3wdpryD8wY0Cdm6PHZ1O8mYoaKgDWkAgZ5b29bcxbIcLSRcXAD4xqj-XOAVWdydCeVheQhtAAGNpcmNsZWRzcXVhcmVyb290Lm92aC8yMDRhMzUwNzQ0YjA1NTA3ZWQ5MTBjOGM1NTlhMTNlZjYxOTg1NDRjN2NjZjI4MWRhYmUxNTUxNmI2ODU2MDEw
[17:05:55]
<Yunohost Git/Infra notifications> [stirling-pdf_ynh] stullekovski opened [issue #37](https://github.com/YunoHost-Apps/stirling-pdf_ynh/issues/37): PDF to word: Error:java.io.IOException - exit code 159
[18:18:19]
<Yunohost Git/Infra notifications> [piped_ynh] orhtej2 merged [pull request #190](https://github.com/YunoHost-Apps/piped_ynh/pull/190): Upgrade to v2025.03.03
[18:18:23]
<Yunohost Git/Infra notifications> [piped_ynh] orhtej2 deleted branch ci-auto-update-2025.03.03
[18:33:36]
<Yunohost Git/Infra notifications> [piped_ynh] yalh76 opened [pull request #191](https://github.com/YunoHost-Apps/piped_ynh/pull/191): Upgrade to v2025.03.03
[18:51:18]
<Yunohost Git/Infra notifications> [piped_ynh] orhtej2 [commented](https://github.com/YunoHost-Apps/piped_ynh/pull/191#issuecomment-2711527080) on [issue #191](https://github.com/YunoHost-Apps/piped_ynh/pull/191) Upgrade to v2025.03.03: Id rather not, the build needed for upgrade is heavy and upstream changes are automated dependency bumps only.
[18:58:03]
<Yunohost Git/Infra notifications> yalh76 renamed repository ums_ynh: UniversalMediaServer : A DLNA, UPnP and HTTP(S) Media Server packaged for YunoHost https://github.com/YunoHost-Apps/ums_ynh
[19:02:27]
<NemStudio18> Hi!
once my app has passed through CI and is validated I have to merge the test branch on the master ynh of the repository? https://ci-apps.yunohost.org/ci/job/15984
[19:03:03]
<Aleks (he/him/il/lui)> yup
[19:03:24]
<NemStudio18> Thx
[19:16:22]
<NemStudio18> sorry to bother you one last time (it's the first time for me) is it normal that the app is still considered broken? https://apps.yunohost.org/app/299ko
[19:18:08]
<Thomas> Yes it will be updated on friday's pr that updates the apps levels
[19:21:28]
<NemStudio18> ok, 👍 I understand the chain better now! thanks for your help!
I have a last question, there is an app that is no longer maintained.
the original project is abandoned but an independent maintains a functional and up-to-date version (php mysql etc),
is it possible to change the sources of the app and become the maintainer too?
[19:22:23]
<Aleks (he/him/il/lui)> what app is it
[19:23:32]
<NemStudio18> Fluxbb
[19:24:26]
<NemStudio18> ( I'm going to put the kids to bed, I'll be right back!)
[20:01:16]
<NemStudio18> I'm back !!!🤘
[20:54:54]
<Max Koder> Hi here !
[20:55:41]
<Max Koder> Thanks for 299Ko :)
[20:58:39]
<NemStudio18> Bienvenue max (le master dev de 299ko)
[21:33:48]
<Yunohost Git/Infra notifications> [synapse_ynh] Josue-T created new branch fix_perm
[21:33:49]
<Yunohost Git/Infra notifications> [synapse_ynh] Josue-T pushed 1 commit to fix_perm: Cleanup legacy label parameter for dynamic permissions ([425cafec](https://github.com/YunoHost-Apps/synapse_ynh/commit/425cafec18dba2f999278a6ab74a72c64e5b0442))
[21:34:58]
<Yunohost Git/Infra notifications> [synapse_ynh] Josue-T opened [pull request #519](https://github.com/YunoHost-Apps/synapse_ynh/pull/519): Cleanup legacy label parameter for dynamic permissions
[21:36:22]
<Yunohost Git/Infra notifications> [synapse_ynh] Josue-T [commented](https://github.com/YunoHost-Apps/synapse_ynh/issues/518#issuecomment-2711903770) on [issue #518](https://github.com/YunoHost-Apps/synapse_ynh/issues/518) Upgrade from 1.123.0~ynh1 to 1.125.0~ynh1 fails: Its a regression from the upstream by https://github.com/YunoHost/yunohost/pull/1917
It suggested a fix on https://git...
[21:36:28]
<Yunohost Git/Infra notifications> [piped_ynh] yalh76 closed [pull request #191](https://github.com/YunoHost-Apps/piped_ynh/pull/191): Upgrade to v2025.03.03
[21:36:39]
<Yunohost Git/Infra notifications> [synapse_ynh] Josue-T assigned Josue-T on [issue #518](https://github.com/YunoHost-Apps/synapse_ynh/issues/518): Upgrade from 1.123.0~ynh1 to 1.125.0~ynh1 fails
[21:36:42]
<Yunohost Git/Infra notifications> [synapse_ynh] Josue-T assigned Josue-T on [pull request #519](https://github.com/YunoHost-Apps/synapse_ynh/pull/519): Cleanup legacy label parameter for dynamic permissions
[21:57:18]
<orhtej2> Thomas: given you contributed some in Funkwhale, any idea why upstream is suddenly gone? cf https://github.com/YunoHost-Apps/funkwhale\_ynh/issues/284
[22:28:10]
<Yunohost Git/Infra notifications> [synapse_ynh] centralscrutinizer21 [commented](https://github.com/YunoHost-Apps/synapse_ynh/issues/518#issuecomment-2711987669) on [issue #518](https://github.com/YunoHost-Apps/synapse_ynh/issues/518) Upgrade from 1.123.0~ynh1 to 1.125.0~ynh1 fails: I see, I am very glad to see how nicely yunohost is progressing as a whole.
Thanks
[22:28:11]
<Yunohost Git/Infra notifications> [synapse_ynh] centralscrutinizer21 closed [issue #518](https://github.com/YunoHost-Apps/synapse_ynh/issues/518): Upgrade from 1.123.0~ynh1 to 1.125.0~ynh1 fails
[23:14:21]
<Yunohost Git/Infra notifications> [mastodon_ynh] yunohost-bot opened [pull request #488](https://github.com/YunoHost-Apps/mastodon_ynh/pull/488): Upgrade to v4.3.5
[23:20:34]
<Yunohost Git/Infra notifications> [stirling-pdf_ynh] yunohost-bot opened [pull request #38](https://github.com/YunoHost-Apps/stirling-pdf_ynh/pull/38): Upgrade to v0.44.1
[23:25:03]
<Yunohost Git/Infra notifications> Autoupdater just ran, here are the results:
- 15 pending update PRs
- 16 new apps PRs
- 14 failed apps updates: appflowy, dynamicqrcode, findmydevice, firefish, gancio, ihatemoney, lemmy, localai, penpot, phpldapadmin, pixelfedglitch, stremio, swingmusic, zwave-js-ui
See the full log here: https://paste.yunohost.org/raw/atamijeson