You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kudu.apache.org by Todd Lipcon <to...@apache.org> on 2016/04/25 20:56:44 UTC
Migrating the website to apache.org
Hi folks,
Migration of the website from github-pages to ASF gitpubsub was one item we
called out in our last podling report but haven't finished yet.
On Friday I put up a script that will help us publish to the new
infrastructure. Would be great to get this reviewed and pushed early this
week so we can complete the migration before our report is due.
http://gerrit.cloudera.org:8080/#/c/2856/
Thanks
-Todd
Re: Migrating the website to apache.org
Posted by Mike Percy <mp...@apache.org>.
I saw Sean Busbey at Apache: Big Data and he mentioned that folks do domain
transfers to the ASF all the time, and ASF infra can keep the redirect
alive forever, so that is certainly an option.
Mike
On Mon, May 2, 2016 at 10:39 AM, Todd Lipcon <to...@cloudera.com> wrote:
> Just to update on this: I filed a JIRA with our ops people to see if we can
> host such a 301 redirect. If that seems difficult for some reason I'll try
> the same avenue with ASF Infra (though would require doing some domain
> transfers, etc)
>
> -Todd
>
> On Tue, Apr 26, 2016 at 6:42 PM, Mike Percy <mp...@apache.org> wrote:
>
> > Also, this is testable without modifying the public CNAME by changing
> one's
> > local /etc/hosts file to point getkudu.io to kudu.i.a.o so we can make
> > sure
> > it works before flipping the DNS on the existing site.
> >
> > On Tue, Apr 26, 2016 at 6:36 PM, Mike Percy <mp...@apache.org> wrote:
> >
> > > I think we could ask ASF infra to add a VirtualHost alias for
> getkudu.io
> > ,
> > > so that if we CNAME getkudu.io to kudu.incubator.apache.org then it
> will
> > > render the same site.
> > >
> > > Then we can use an .htaccess file with RedirectMatch or RewriteRule
> > > directives to implement a 301 redirect from getkudu.io/* to
> kudu.i.a.o/*
> > >
> > > I would prefer to keep the branch called gh-pages since for the
> > templating
> > > that remains github-compatible it stays easy to push to github for
> Gerrit
> > > reviewers to look at without having to download the patch and render
> the
> > > site themselves.
> > >
> > > Mike
> > >
> > > On Tue, Apr 26, 2016 at 10:05 AM, Todd Lipcon <to...@apache.org> wrote:
> > >
> > >> Thanks, Mike, for reviewing the publishing tool last night.
> > >>
> > >> Here are the remaining steps I'd propose:
> > >>
> > >> 1) publish the site to kudu.incubator.apache.org (while still keeping
> > the
> > >> current github-hosted site)
> > >> 2) if that looks good, make a new branch called 'site' starting from
> the
> > >> current 'gh-pages' branch, which we'll use for site changes going
> > forward.
> > >> 3) make a commit to 'gh-pages' so that the getkudu.io site redirects
> to
> > >> kudu.incubator.apache.org
> > >>
> > >> Does that make sense? One thing i want to make sure is that old links
> to
> > >> getkudu.io/foo.html continue to redirect properly to
> > >> kudu.incubator.apache.org/foo.html with the appropriate status code.
> > That
> > >> might not be achievable with github pages -- do we need to host our
> own
> > >> redirect server somewhere? Maybe infra could host that for us? Any
> > ideas?
> > >>
> > >> -Todd
> > >>
> > >> On Mon, Apr 25, 2016 at 11:56 AM, Todd Lipcon <to...@apache.org>
> wrote:
> > >>
> > >> > Hi folks,
> > >> >
> > >> > Migration of the website from github-pages to ASF gitpubsub was one
> > item
> > >> > we called out in our last podling report but haven't finished yet.
> > >> >
> > >> > On Friday I put up a script that will help us publish to the new
> > >> > infrastructure. Would be great to get this reviewed and pushed early
> > >> this
> > >> > week so we can complete the migration before our report is due.
> > >> >
> > >> > http://gerrit.cloudera.org:8080/#/c/2856/
> > >> >
> > >> > Thanks
> > >> > -Todd
> > >> >
> > >>
> > >>
> > >>
> > >> --
> > >> Todd Lipcon
> > >> Software Engineer, Cloudera
> > >>
> > >
> > >
> >
>
>
>
> --
> Todd Lipcon
> Software Engineer, Cloudera
>
Re: Migrating the website to apache.org
Posted by Todd Lipcon <to...@cloudera.com>.
Just to update on this: I filed a JIRA with our ops people to see if we can
host such a 301 redirect. If that seems difficult for some reason I'll try
the same avenue with ASF Infra (though would require doing some domain
transfers, etc)
-Todd
On Tue, Apr 26, 2016 at 6:42 PM, Mike Percy <mp...@apache.org> wrote:
> Also, this is testable without modifying the public CNAME by changing one's
> local /etc/hosts file to point getkudu.io to kudu.i.a.o so we can make
> sure
> it works before flipping the DNS on the existing site.
>
> On Tue, Apr 26, 2016 at 6:36 PM, Mike Percy <mp...@apache.org> wrote:
>
> > I think we could ask ASF infra to add a VirtualHost alias for getkudu.io
> ,
> > so that if we CNAME getkudu.io to kudu.incubator.apache.org then it will
> > render the same site.
> >
> > Then we can use an .htaccess file with RedirectMatch or RewriteRule
> > directives to implement a 301 redirect from getkudu.io/* to kudu.i.a.o/*
> >
> > I would prefer to keep the branch called gh-pages since for the
> templating
> > that remains github-compatible it stays easy to push to github for Gerrit
> > reviewers to look at without having to download the patch and render the
> > site themselves.
> >
> > Mike
> >
> > On Tue, Apr 26, 2016 at 10:05 AM, Todd Lipcon <to...@apache.org> wrote:
> >
> >> Thanks, Mike, for reviewing the publishing tool last night.
> >>
> >> Here are the remaining steps I'd propose:
> >>
> >> 1) publish the site to kudu.incubator.apache.org (while still keeping
> the
> >> current github-hosted site)
> >> 2) if that looks good, make a new branch called 'site' starting from the
> >> current 'gh-pages' branch, which we'll use for site changes going
> forward.
> >> 3) make a commit to 'gh-pages' so that the getkudu.io site redirects to
> >> kudu.incubator.apache.org
> >>
> >> Does that make sense? One thing i want to make sure is that old links to
> >> getkudu.io/foo.html continue to redirect properly to
> >> kudu.incubator.apache.org/foo.html with the appropriate status code.
> That
> >> might not be achievable with github pages -- do we need to host our own
> >> redirect server somewhere? Maybe infra could host that for us? Any
> ideas?
> >>
> >> -Todd
> >>
> >> On Mon, Apr 25, 2016 at 11:56 AM, Todd Lipcon <to...@apache.org> wrote:
> >>
> >> > Hi folks,
> >> >
> >> > Migration of the website from github-pages to ASF gitpubsub was one
> item
> >> > we called out in our last podling report but haven't finished yet.
> >> >
> >> > On Friday I put up a script that will help us publish to the new
> >> > infrastructure. Would be great to get this reviewed and pushed early
> >> this
> >> > week so we can complete the migration before our report is due.
> >> >
> >> > http://gerrit.cloudera.org:8080/#/c/2856/
> >> >
> >> > Thanks
> >> > -Todd
> >> >
> >>
> >>
> >>
> >> --
> >> Todd Lipcon
> >> Software Engineer, Cloudera
> >>
> >
> >
>
--
Todd Lipcon
Software Engineer, Cloudera
Re: Migrating the website to apache.org
Posted by Mike Percy <mp...@apache.org>.
Also, this is testable without modifying the public CNAME by changing one's
local /etc/hosts file to point getkudu.io to kudu.i.a.o so we can make sure
it works before flipping the DNS on the existing site.
On Tue, Apr 26, 2016 at 6:36 PM, Mike Percy <mp...@apache.org> wrote:
> I think we could ask ASF infra to add a VirtualHost alias for getkudu.io,
> so that if we CNAME getkudu.io to kudu.incubator.apache.org then it will
> render the same site.
>
> Then we can use an .htaccess file with RedirectMatch or RewriteRule
> directives to implement a 301 redirect from getkudu.io/* to kudu.i.a.o/*
>
> I would prefer to keep the branch called gh-pages since for the templating
> that remains github-compatible it stays easy to push to github for Gerrit
> reviewers to look at without having to download the patch and render the
> site themselves.
>
> Mike
>
> On Tue, Apr 26, 2016 at 10:05 AM, Todd Lipcon <to...@apache.org> wrote:
>
>> Thanks, Mike, for reviewing the publishing tool last night.
>>
>> Here are the remaining steps I'd propose:
>>
>> 1) publish the site to kudu.incubator.apache.org (while still keeping the
>> current github-hosted site)
>> 2) if that looks good, make a new branch called 'site' starting from the
>> current 'gh-pages' branch, which we'll use for site changes going forward.
>> 3) make a commit to 'gh-pages' so that the getkudu.io site redirects to
>> kudu.incubator.apache.org
>>
>> Does that make sense? One thing i want to make sure is that old links to
>> getkudu.io/foo.html continue to redirect properly to
>> kudu.incubator.apache.org/foo.html with the appropriate status code. That
>> might not be achievable with github pages -- do we need to host our own
>> redirect server somewhere? Maybe infra could host that for us? Any ideas?
>>
>> -Todd
>>
>> On Mon, Apr 25, 2016 at 11:56 AM, Todd Lipcon <to...@apache.org> wrote:
>>
>> > Hi folks,
>> >
>> > Migration of the website from github-pages to ASF gitpubsub was one item
>> > we called out in our last podling report but haven't finished yet.
>> >
>> > On Friday I put up a script that will help us publish to the new
>> > infrastructure. Would be great to get this reviewed and pushed early
>> this
>> > week so we can complete the migration before our report is due.
>> >
>> > http://gerrit.cloudera.org:8080/#/c/2856/
>> >
>> > Thanks
>> > -Todd
>> >
>>
>>
>>
>> --
>> Todd Lipcon
>> Software Engineer, Cloudera
>>
>
>
Re: Migrating the website to apache.org
Posted by Mike Percy <mp...@apache.org>.
I think we could ask ASF infra to add a VirtualHost alias for getkudu.io,
so that if we CNAME getkudu.io to kudu.incubator.apache.org then it will
render the same site.
Then we can use an .htaccess file with RedirectMatch or RewriteRule
directives to implement a 301 redirect from getkudu.io/* to kudu.i.a.o/*
I would prefer to keep the branch called gh-pages since for the templating
that remains github-compatible it stays easy to push to github for Gerrit
reviewers to look at without having to download the patch and render the
site themselves.
Mike
On Tue, Apr 26, 2016 at 10:05 AM, Todd Lipcon <to...@apache.org> wrote:
> Thanks, Mike, for reviewing the publishing tool last night.
>
> Here are the remaining steps I'd propose:
>
> 1) publish the site to kudu.incubator.apache.org (while still keeping the
> current github-hosted site)
> 2) if that looks good, make a new branch called 'site' starting from the
> current 'gh-pages' branch, which we'll use for site changes going forward.
> 3) make a commit to 'gh-pages' so that the getkudu.io site redirects to
> kudu.incubator.apache.org
>
> Does that make sense? One thing i want to make sure is that old links to
> getkudu.io/foo.html continue to redirect properly to
> kudu.incubator.apache.org/foo.html with the appropriate status code. That
> might not be achievable with github pages -- do we need to host our own
> redirect server somewhere? Maybe infra could host that for us? Any ideas?
>
> -Todd
>
> On Mon, Apr 25, 2016 at 11:56 AM, Todd Lipcon <to...@apache.org> wrote:
>
> > Hi folks,
> >
> > Migration of the website from github-pages to ASF gitpubsub was one item
> > we called out in our last podling report but haven't finished yet.
> >
> > On Friday I put up a script that will help us publish to the new
> > infrastructure. Would be great to get this reviewed and pushed early this
> > week so we can complete the migration before our report is due.
> >
> > http://gerrit.cloudera.org:8080/#/c/2856/
> >
> > Thanks
> > -Todd
> >
>
>
>
> --
> Todd Lipcon
> Software Engineer, Cloudera
>
Re: Migrating the website to apache.org
Posted by Todd Lipcon <to...@apache.org>.
Thanks, Mike, for reviewing the publishing tool last night.
Here are the remaining steps I'd propose:
1) publish the site to kudu.incubator.apache.org (while still keeping the
current github-hosted site)
2) if that looks good, make a new branch called 'site' starting from the
current 'gh-pages' branch, which we'll use for site changes going forward.
3) make a commit to 'gh-pages' so that the getkudu.io site redirects to
kudu.incubator.apache.org
Does that make sense? One thing i want to make sure is that old links to
getkudu.io/foo.html continue to redirect properly to
kudu.incubator.apache.org/foo.html with the appropriate status code. That
might not be achievable with github pages -- do we need to host our own
redirect server somewhere? Maybe infra could host that for us? Any ideas?
-Todd
On Mon, Apr 25, 2016 at 11:56 AM, Todd Lipcon <to...@apache.org> wrote:
> Hi folks,
>
> Migration of the website from github-pages to ASF gitpubsub was one item
> we called out in our last podling report but haven't finished yet.
>
> On Friday I put up a script that will help us publish to the new
> infrastructure. Would be great to get this reviewed and pushed early this
> week so we can complete the migration before our report is due.
>
> http://gerrit.cloudera.org:8080/#/c/2856/
>
> Thanks
> -Todd
>
--
Todd Lipcon
Software Engineer, Cloudera