01:34:42 check cashed? 07:02:18 I've updated the dns records to v0.18.2.0 09:40:57 binaryFate: did you deploy the website? 09:41:09 otherwise the auto updater doesn't work 10:14:44 there are also some prs to merge (ping luigi1111) 10:46:57 Just opened a very important issue for the future of the repo. Please read and provide feedback: https://github.com/monero-project/monero-site/issues/2140 11:44:07 I think switching to Hugo is a good idea ^ 11:45:28 You'll never have any issues with dependencies. I personally have converted several websites to Hugo and it's not that hard when you understand how Hugo works. 11:46:56 The community is probably more active than Jekyll's at this point too. The only thing I can't fully comment on is localization. I used it years ago and don't remember having any problems. 11:57:24 having some first hand experience with -site and translation files, imo making the process easier / small changes feasible is fundamental to the monero project. if Hugo can achieve this then its worth the effort 12:00:24 s/The conversion to jekyll would/The conversion to Hugo would 12:02:18 Hugo can work with weblate. Although I'd prefer if you simply accepted merge requests. Weblate was abandoned for months and translations for many languages are still stalled/not applied. Just release the changes from your dungeon, k thanks. 13:10:19 I haven't deployed anything yet. Is luigi all done? 13:14:05 yes 13:31:16 mmm so nothing to merge 13:42:23 "Hugo can work with weblate..." <- There will be a new coordinator for the localization workgroup soon. We are waiting for my access to be restored and then the new coordinator will also get credentials and thing will be in motion again. 13:45:37 btw the biggest amount of work to do would be to convert moneropedia and user guides for each language, but that could be probably be automated a fair bit 13:47:26 binaryFate: there are some prs to merge, but nothing urgent, so imo not worth waiting 13:55:27 deployed, but I can't flush cache right now cloudflare is crashing(!). I keep trying 14:04:09 ok flushed, cdn too 14:04:11 all done 14:32:03 binaryFate: sorry, I meant all done with auto updater 14:32:08 I didn't think of merges 14:32:30 but seems nothing urgent anyway 14:33:41 ah luigi just merged 😛 16:08:02 he had merged before, we're good 17:12:26 Is there a cache option for Hugo? I use Hugo on my personal website. It takes about 10 seconds to build each time. I have big data files that probably slow down the build. 17:13:21 we are now providing hugo tech support , lets get learning 17:15:25 #2140 claims that Hugo build times are measured in milliseconds. I'm providing a counterexample. 17:17:01 10 seconds to build site would be a huge improvement 17:18:23 My website isn't as complex as getmonero.org :P 17:20:47 "Is there a cache option for Hugo..." <- Can't relate to this, for me also milliseconds. 17:21:08 the build times are not the issue (even if they stayed the same) for me its more 'editing simple sentences' that are translated etc 17:21:33 Your data files have to do with that. And Jekyll in Ruby would take even longer for you :D 17:21:49 Or maybe you generate graphs using an external program or something like that 17:22:14 ive just done a quick 5 min search on.. hugo localisation... convert jekyll to hugo etc and im feeling sleepy 17:22:50 we used --limit-posts 2 (to quicken the build up) at the moment 17:29:16 My /static directory for Hugo is about 2.3GB. It's zip files and one large raw HTML file. I am saying to make sure that Hugo actually scales up. 17:31:11 Do you build with --gc --minify? 17:35:43 No. Just tried. They increased the build time by about 30% 17:38:59 Yeah minifying files and deleting old cache afterwards take longer. Was wondering if you were doing this already.