[GitHub] [groovy-website] paulk-asert commented on issue #10: SSL Certificate not signed by a standard certificate authority
paulk-asert commented on issue #10: SSL Certificate not signed by a standard certificate authority URL: https://github.com/apache/groovy-website/issues/10#issuecomment-498107586 We still need to move the site but for now we have an SSL certificate in place using https://letsencrypt.org/getting-started/. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [groovy-website] paulk-asert commented on issue #10: SSL Certificate not signed by a standard certificate authority
paulk-asert commented on issue #10: SSL Certificate not signed by a standard certificate authority URL: https://github.com/apache/groovy-website/issues/10#issuecomment-497450454 Groovy's repos are here: https://gitbox.apache.org/repos/asf Currently the :site-dev:generateSite task in the groovy-website repo is used to build the dev site. I manually copy the generated content into the groovy-dev-site (asf-site branch) and then commit. We have tasks in the groovy-release gradle build files that do such git operations. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [groovy-website] paulk-asert commented on issue #10: SSL Certificate not signed by a standard certificate authority
paulk-asert commented on issue #10: SSL Certificate not signed by a standard certificate authority URL: https://github.com/apache/groovy-website/issues/10#issuecomment-497446851 Fixing the user site is a couple of steps away. I may not get to look at it for some weeks. Next step is getting dev site properly automatic. In the groovy-website repo there is a gradle build which produces the site zip. We need to add another task to check that into the groovy-dev-site repo as a fresh check in. We can probably reuse some task defns from the groovy-release repo. It will need someone with Apache credentials to test. Fixing the user site will then be a replication of this but with a bit more work first and won't build a total replacement but additions for each release as well as some content which is replaced whenever we rebuild the site. Plus we need to liaise with Apache infra to get the new site in place... This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
