visch commented on issue #10: SSL Certificate not signed by a standard certificate authority URL: https://github.com/apache/groovy-website/issues/10#issuecomment-497679447 I understand the problem now, messed with things. Unfortunately only had 20 minutes this morning. Next steps: 1. follow groovy-releases lead to get the groovy-website site-dev:generateSite build to publish (copy groovy-website/site-dev/build/site$ to the groovy-dev-site (branch asf-site) repo 2. Add a site-dev:publishSite task to groovy-website with env variables for apache creds (test with local git creds) This weekend looks much more promising for me to have time to do this (if someone else can beat me feel free). What I"m unsure about is how auto publishing impacts the SSL cert being updated on . Is there some way we can short cut all of this to just get the SSL cert updated? Maybe we could push some notice up to the main site to say "use http://www.groovy-lang.org/ while we're in process updating the site hosting provider" I'll follow regardless as I'm sure there's reasons, let me know if there's anything else I can do!
---------------------------------------------------------------- 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
