Re: Moving Groovy site onto ASF Infra

Yesterday, I did change the apache2 server restart timing to 4 times a
day instead of daily (was originally weekly), but it seems teamcity
still hogs the machine so much that it causes problems for the apache2
side of things plus we have had some denial of service attacks.

But it is time to move this. It is all on our side not infra in the
first instance. Recently, I have been holding off waiting for us to
move our build processes to be more like Grails but maybe we shouldn't
wait any longer.

We already have a repo https://github.com/apache/groovy-user-site
which we need to make more like
https://github.com/apache/groovy-dev-site. The dev site is fully
generated, but the user site has a bunch of legacy content we need to
also move and not lose as we generate new content. And we need our
release processes to store new versions of our doco there upon each
release. So we need to update those scripts too. Once we have all that
in place, we can put in an infra ticket to get the DNS stuff sorted.
ci.groovy-lang.org would be the only thing that stays put.

There is another option which is to rework the content on the two
sites to essentially put all the content within the current dev site
and just make groovy-lang.org be an alias for groovy.apache.org. There
would be some conflicts to sort out and similar changes needed for the
release scripts.

Paul.

On Wed, Aug 26, 2026 at 7:54 AM Jonny <[email protected]> wrote:
>
> 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 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). 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 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