Moving Groovy site onto ASF Infra
Jonny <[email protected]>
| Newsgroups | gmane.comp.lang.groovy.devel |
|---|---|
| Message-ID | <CANkfqQMXHrbOjvbBK=MvbhGNO+cNYqoUudr4Q2WkVqNTno2gug@mail.gmail.com> |
Hey, everyone. Right now, the groovy website is hosted on a mix of Apache infrastructure and a legacy box. The groovy-lang.org portion of the site seems to go down with some regularity (it's not loading for me right now). I know that Paul setup a daily restart <https://lists.apache.org/thread/w7t5v2p9gjr09cb7pbbh43vl6sfj0p0g> back in March to try and address that, but that's only a temporary solution and it's obviously not 100%. Do we need someone to chase up an infra ticket around moving the whole site onto ASF infra? We did something like this with Geb, preserving links from the old gebish.org domain using [mod_rewrite] rules (see INFRA-26562 <https://issues.apache.org/jira/browse/INFRA-26562>). I wouldn't want to make the move if it meant breaking a bunch of links to the Groovy site, but in this case I think we can basically keep our existing links while still moving the content over to ASF's hosting, so long as the infra team agrees. We've already got https://groovy.apache.org/, so it shouldn't be a problem to add content to that and setup appropriate rewrite rules. Personally, I'd rather leave the business of hosting the site to the good folks on the ASF Infra team so we can focus on other stuff. I'm still getting caught up on the mailing list, so I'm a little sheepish about volunteering for this in the midst of a major release, but the site being down was getting on my nerves so I'm trying to follow my round tuits <https://en.wiktionary.org/wiki/round_tuit> where they lead me. There are two questions: 1. Would anyone object to my opening a ticket with the INFRA team to do this? 2. Should this have its own VOTE thread? Best, Jonny