09:39:14 Hi folks. I've been testing netlify to deploy a preview of incoming PR, so that people can see a live preview right away. 09:39:46 Basically one we get a PR, netlify builds and deploys it. Then it posts a comment under the PR with a link to the preview of the built PR. 09:40:28 we spoke about it some time ago. It's a cool feature to have because allows people with no build environment to see the results of a PR right away. 09:41:21 I think we can integrate it quite soon. The configuration is quite straightforward, but we would need to give netlify permissions on github. 09:43:01 Right now the build time of a PR is ~30 minutes. It should be less after #1014, since most of the time is spent in post-processing tasks (the website itself builds in like 15 min). 09:43:39 My test configuration was very minimal (i only specified a ruby version to speedup things), but i think with some tweaking we can reduce the amount necessary to build. 09:43:57 Not of really much, because building all those blog posts requires times, but still something. 09:44:51 What do people think about it? IMO we could use it quite soon (once i'm done testing i would say) 09:48:16 We could also use github works to deploy the netlify preview, but i haven't looked into it yet. 09:49:14 I made a test PR on my fork on github, will post it here once the preview is deployed, to show how it would look like on the upstream repo 09:49:31 oh. Just finished :) 09:49:33 https://github.com/erciccione/monero-site/pull/4 09:50:07 logs: https://app.netlify.com/sites/monero-site-preview/deploys/5ecf81e937327b0007ab8fa2 09:57:08 To sum up: It's very cool and i think we should implement it. I think could also push people to contribute more, since a dedicated test environment won't be strictly necessary anymore 09:58:05 neat 09:58:10 is netlify free? 10:27:05 yep 11:21:56 that is awesome, great stuff ErCiccione[m] 11:48:55 :) 11:49:24 the only meaningful limit for the free plan is the "300 build minutes/month" 11:51:26 Now i just managed to have a build compiled and deployed in 10 minutes. I don't think we can go lower than that, except by reducing the amount fo blog posts loaded. Which could make sense 12:00:28 Limiting the blog posts to 10 we build and deploy the preview in 4 minutes (cached. the first build would take much more ). I think that would be fine 12:01:03 Alright. I'll see if makes sense to put my few edits in a config file, after that we can already integrate it imo. 12:01:34 The important is to not go beyond the 300 build minutes/month limit. But if we build in 4 minutes we should be fine. 12:02:54 can you make it build just one page? so in the PR someone could mention whatever.html and get a link to that? 12:04:21 I don't think so. At the end netlify simply deploys jekyll. And you cannot build a single page with jekyll 12:04:57 btw if we surpass the 300 build minutes/month limit it will be $45 /month 12:05:41 we would have 1000 build minutes/month and 3 concurrent builds 12:32:13 Ok. Final tests say 4-5 minutes to build + deploy without caching and ~4 with caching. Assuming the usual volume of PRs and considering that we get a new deployment with each new commit pushed or force pushed to a PR, we should be within the range for the free account by a lot. 16:28:28 .merge+ #1014 #1013 16:28:29 Added 16:28:33 .merges 16:28:33 -xmr-pr- #1004 #1010 #1013 #1014 #986 #988 #994 17:23:53 what is the point of 1010? 17:26:18 encouraging subaddresses 17:47:52 mm, ok 18:35:34 and also China 18:35:35 :-P