www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tony Stevenson (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (INFRA-3695) archive.apachecon.com
Date Mon, 20 Jun 2011 08:11:47 GMT

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

Tony Stevenson closed INFRA-3695.

    Resolution: Fixed

Ok, the site has been converted to subpub.  

I have edited the svn authz template to make the folder * = r
I have added the httpd vhost config (AddType has been removed) 
DNS has been updated to point to eos (need to wait for caches to expire) 

So within an hour or two this should start working.

> archive.apachecon.com
> ---------------------
>                 Key: INFRA-3695
>                 URL: https://issues.apache.org/jira/browse/INFRA-3695
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: DNS, Website
>            Reporter: Nick Burch
>            Assignee: Tony Stevenson
>            Priority: Minor
> As discussed initially on infrastructure@ a few months back, hosting of old ApacheCon
sites is our responsibility and not the producers. As such, I've been collecting as many of
the old sites as possible (from backups, archives etc), and we now have something ready to
be hosted
> All of the old sites so far are able to reside on a single vhost, hosting static content.
This is available at https://svn.apache.org/repos/infra/apachecon/archive.apachecon.com
> Could we please setup a vhost + dns for archive.apachecon.com serving this?
> This site would also want to be an alias for a few of the older apachecon dns entries
too, such as eu.apachecon.com. These are listed in site.conf, along with a few bits of httpd
vhost config that are needed to allow certain things to continue working without needing to
change their URLs
> concom will be the pmc overseeing this. If we can use svnpubsub then that'd probably
be easiest, so we don't need any shell access to update things

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message