infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul King (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-17187) Moving Groovy website repo
Date Tue, 30 Oct 2018 07:16:00 GMT

     [ https://issues.apache.org/jira/browse/INFRA-17187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Paul King updated INFRA-17187:
------------------------------
    Description: 
Hi, we have had a long outstanding task to move the Groovy user site from an external box
to an internal one. We also have a dev site which is internal but might need to be moved as
part of above. I'll include some details here and we can spin off further tasks if appropriate.

Currently the source for both websites is in (I'll refer to this repo as GITHUB_SRC):

https://github.com/groovy/groovy-website

The content for the user site is generated using gradle by running the following command from
the root of that repo:

> gradlew :site-user:generateSite

or (invokes above plus checks deadlinks plus creates a zip)

> gradlew :site-user:webzip

This leaves the website content in:

site-user/build/site

Similarly, the dev site is generated using:

> gradlew :site-dev:webzip

Which leaves the website content in:

site-dev/build/site

Currently the dev site (groovy.apache.org) content is manually placed into the asf-site branch
of the following repo (I'll call this ASF_SRC):

http://git-wip-us.apache.org/repos/asf/groovy-website.git

We have also created two new repos. The first I'll call ASF_DEV:

http://git-wip-us.apache.org/repos/asf/groovy-dev-site.git

The second I'll call ASF_USER:

http://git-wip-us.apache.org/repos/asf/groovy-user-site.git

What I'd like to do is:
* re-purpose the ASF_SRC repo to be a copy of GITHUB_SRC.
* point groovy.apache.org to ASF_DEV (instead of ASF_SRC)
(That repo is currently a direct copy of ASF_SRC so this could be done immediately)
* ultimately point groovy-lang.org to ASF_USER (use of this domain has been approved a long
time ago and has already been transferred to ASF some time ago)

The last bullet point might take a little while to verify contents has happened smoothly so
perhaps some temp hostname/port could be used until we are ready to turn on the new hosting
arrangement.

As mentioned earlier, there are gradle tasks for building the sites - if we can set up some
kind of build robot to automatically place the contents in the correct spot, we are very open
to suggestions. We aren't wedded to necessarily using the asf-site branch approach if some
other alternative is appropriate.

  was:
Hi, we have had a long outstanding task to move the Groovy user site from an external box
to an internal one. We also have a dev site which is internal but might need to be moved as
part of above. I'll include some details here and we can spin off further tasks if appropriate.

Currently the source for both websites is in (I'll refer to this repo as GITHUB_SRC):

https://github.com/groovy/groovy-website

The content for the user site is generated using gradle by running the following command from
the root of that repo:

> gradlew :site-user:generateSite

or (invokes above plus checks deadlinks plus creates a zip)

> gradlew :site-user:webzip

This leaves the website content in:

site-user/build/site

Similarly, the dev site is generated using:

> gradlew :site-dev:webzip

Which leaves the website content in:

site-dev/build/site

Currently the dev site (groovy.apache.org) content is manually placed into the asf-site branch
of the following repo (I'll call this ASF_SRC):

http://git-wip-us.apache.org/repos/asf/groovy-website.git

We have also created two new repos. The first I'll call ASF_DEV:

http://git-wip-us.apache.org/repos/asf/groovy-dev-site.git

The second I'll call ASF_USER:

http://git-wip-us.apache.org/repos/asf/groovy-user-site.git

What I'd like to do is:
* re-purpose the ASF_SRC repo to be a copy of GITHUB_SRC.
* point groovy.apache.org to ASF_DEV (instead of ASF_SRC)
(That repo is currently a direct copy from the asf groovy-website repo so this could be done
immediately)
* ultimately point groovy-lang.org to ASF_USER (use of this domain has been approved a long
time ago and has already been transferred to ASF some time ago)

The last bullet point might take a little while to verify contents has happened smoothly so
perhaps some temp hostname/port could be used until we are ready to turn on the new hosting
arrangement.

As mentioned earlier, there are gradle tasks for building the sites - if we can set up some
kind of build robot to automatically place the contents in the correct spot, we are very open
to suggestions. We aren't wedded to necessarily using the asf-site branch approach if some
other alternative is appropriate.


> Moving Groovy website repo
> --------------------------
>
>                 Key: INFRA-17187
>                 URL: https://issues.apache.org/jira/browse/INFRA-17187
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Github, Website
>            Reporter: Paul King
>            Priority: Major
>
> Hi, we have had a long outstanding task to move the Groovy user site from an external
box to an internal one. We also have a dev site which is internal but might need to be moved
as part of above. I'll include some details here and we can spin off further tasks if appropriate.
> Currently the source for both websites is in (I'll refer to this repo as GITHUB_SRC):
> https://github.com/groovy/groovy-website
> The content for the user site is generated using gradle by running the following command
from the root of that repo:
> > gradlew :site-user:generateSite
> or (invokes above plus checks deadlinks plus creates a zip)
> > gradlew :site-user:webzip
> This leaves the website content in:
> site-user/build/site
> Similarly, the dev site is generated using:
> > gradlew :site-dev:webzip
> Which leaves the website content in:
> site-dev/build/site
> Currently the dev site (groovy.apache.org) content is manually placed into the asf-site
branch of the following repo (I'll call this ASF_SRC):
> http://git-wip-us.apache.org/repos/asf/groovy-website.git
> We have also created two new repos. The first I'll call ASF_DEV:
> http://git-wip-us.apache.org/repos/asf/groovy-dev-site.git
> The second I'll call ASF_USER:
> http://git-wip-us.apache.org/repos/asf/groovy-user-site.git
> What I'd like to do is:
> * re-purpose the ASF_SRC repo to be a copy of GITHUB_SRC.
> * point groovy.apache.org to ASF_DEV (instead of ASF_SRC)
> (That repo is currently a direct copy of ASF_SRC so this could be done immediately)
> * ultimately point groovy-lang.org to ASF_USER (use of this domain has been approved
a long time ago and has already been transferred to ASF some time ago)
> The last bullet point might take a little while to verify contents has happened smoothly
so perhaps some temp hostname/port could be used until we are ready to turn on the new hosting
arrangement.
> As mentioned earlier, there are gradle tasks for building the sites - if we can set up
some kind of build robot to automatically place the contents in the correct spot, we are very
open to suggestions. We aren't wedded to necessarily using the asf-site branch approach if
some other alternative is appropriate.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message