[10:40:24]
<Yunohost Git/Infra notifications> [landingpage] mrflos merged [pull request #31](https://github.com/YunoHost/landingpage/pull/31): fix(design): equal height columns
[10:46:57]
<Yunohost Git/Infra notifications> [landingpage] alexAubin deleted branch equal-height-columns
[10:48:30]
<mrflos> ale ks is there CI/CD for the landing page or a manual action is needed?
[10:52:01]
<Aleks (he/him/il/lui)> right now manual action is needed and somebody should find the courage to add a damn cron job x_x
[12:03:54]
<mrflos> > <@Alekswag:matrix.org> right now manual action is needed and somebody should find the courage to add a damn cron job x_x
i have not enought rights for accessing the server but i can help with ci/cd if we go this way
[13:47:29]
<Salamandar> > <@mrfloss:matrix.org> ale ks is there CI/CD for the landing page or a manual action is needed?
If you have any idea about how to trigger the landingpage rebuild from CI instead of a simple cron, i'll take it
[13:49:21]
<Salamandar> also hmmm for the landingpage i think i'd prefer a human action because if by any chance the last `main` commit is broken, at least there's already someone connected to fix/revert
[14:15:04]
<Aleks (he/him/il/lui)> @_@
[14:15:20]
<Aleks (he/him/il/lui)> that's just like super inconvenient ...
[14:16:07]
<Aleks (he/him/il/lui)> we have crons for dozens of things like app catalog rebuild, app store, ci scheduling etc
[14:16:24]
<Salamandar> yes yes
[14:16:30]
<Salamandar> but landingpage feels more "critical" to me
[14:16:55]
<Salamandar> but I can put it if you want
[14:17:10]
<Aleks (he/him/il/lui)> it's not like there's many reasons tha it crashes and worst case scenario we'll get a monitoring notification here + cron job failiture by email ...
[14:50:22]
<mrflos> i was thinking of cd/ci like this:
[14:51:41]
<mrflos> - push on main branch : deploy test website
- tag creation: deploy on production website
[14:51:58]
<mrflos> you can even add a button for deploy, but no need with this tag creation
[14:52:44]
<mrflos> you can check on test site your latest commit, then if all good, create a tag to deploy on prod
[15:43:31]
<Aleks (he/him/il/lui)> ... or we can just create a cron job like we already do for dozen of stuff and it does the job @_@
[15:45:03]
<Salamandar> > <@Alekswag:matrix.org> ... or we can just create a cron job like we already do for dozen of stuff and it does the job @_@
there are no cron jobs anymore
[15:45:45]
<Aleks (he/him/il/lui)> jesus christ, yes, "systemd timer", whatever, cron is easier to write
[15:46:23]
<Salamandar> :D
[15:59:58]
<Salamandar> Thu 2024-11-28 17:01:27 CET 1min 49s left - - landingpage-update.timer landingpage-update.service
[16:01:57]
<mrflos> i'm not sure that creating hand made updater that don't permit to cotnrol the deployments, and need some extra configuration for servers is the best way to do thing, but whatever
[16:02:08]
<Salamandar> > <@mrfloss:matrix.org> i'm not sure that creating hand made updater that don't permit to cotnrol the deployments, and need some extra configuration for servers is the best way to do thing, but whatever
not sure i understand
[16:02:30]
<Salamandar> but i might agree with you
[16:03:59]
<mrflos> tldr:
cron for git update service < classic ci/cd from git forge
[16:04:13]
<mrflos> but not so important
[16:04:29]
<Salamandar> yeah I agree
[16:04:29]
<Salamandar> but how ?
[16:04:40]
<Salamandar> do we give the github CI ssh creds ?
[16:04:40]
<Salamandar> "meh"
[16:05:21]
<mrflos> very local user that can only scp in the good folder?
[16:06:32]
<Salamandar> so the actual build would be done on CI, and only a copy of the very final files would be done ?
[16:06:37]
<Salamandar> sounds ok to me
[16:07:54]
<mrflos> i'm busy this week but i can make a pr as a POC
[17:41:37]
<Yunohost Git/Infra notifications> [yunohost-admin] yunohost-bot opened [pull request #600](https://github.com/YunoHost/yunohost-admin/pull/600): Translations update from Weblate