| Time |
Nick |
Message |
| 00:27 |
MTDiscord |
<wsor4035> so..... i need to update deps on the main site. i can have dependabot make prs for me, and there is a build ci action. so i could just yolo approve them..... |
| 00:27 |
MTDiscord |
<wsor4035> ...mainly cause i dont want to have to set ruby up |
| 00:30 |
MTDiscord |
<wsor4035> alternatively, could convert it to using hugo |
| 00:30 |
MTDiscord |
<wsor4035> ||which isnt that bad of an idea since there is that long running issue for translation that it would solve|| |
| 01:25 |
MTDiscord |
<mark.wiemer> For now let's update the deps, probably make an issue to convert it to Hugo. I can't imagine any full-site conversion being easy, and if deps are vulnerable let's patch that leak before we build a new boat |
| 01:25 |
MTDiscord |
<mark.wiemer> I think it's worth setting up Ruby locally to make sure we don't bring down the main site for ~30 minutes while we try to rollback any bad changes |
| 01:28 |
MTDiscord |
<wsor4035> its a static site, so its who cares on anything live. more so for anyone running it on dev |
| 04:00 |
|
MTDiscord joined #luanti-docs |
| 11:18 |
MTDiscord |
<mark.wiemer> I'm confused. If we break something and deploy it blindly, won't that break people's experience when the try to go to luanti.org ? Even static sites can break. Updating deps might break styles, or links, or something else, right? |
| 11:20 |
MTDiscord |
<mark.wiemer> Or do you mean it's not vulnerable? In that case, that makes sense. Why do you say you "have to" update the deps then? |
| 11:40 |
rubenwardy |
if the build passes it's probably fine |
| 11:40 |
rubenwardy |
you should still probably test locally though |
| 11:40 |
rubenwardy |
especially if the updates aren't just patch updates |
| 18:18 |
|
Desour joined #luanti-docs |
| 19:09 |
|
[MatrxMT] joined #luanti-docs |
| 19:12 |
|
[MatrxMT] joined #luanti-docs |
| 19:35 |
|
GreenXenith joined #luanti-docs |
| 21:14 |
MTDiscord |
<wsor4035> re https://github.com/luanti-org/luanti/pull/15951#pullrequestreview-2726542388 we probably should eventually consider if the engine repo should have /docs, or what in it, etc. since it doesnt make much sense to have duplicated stuff/split accross two places, etc |
| 21:15 |
MTDiscord |
<luatic> i agree |
| 23:32 |
|
MTDiscord1 joined #luanti-docs |
| 23:43 |
|
MTDiscord joined #luanti-docs |
| 23:44 |
|
GreenXenith joined #luanti-docs |
