WWW migration

[Auke Jilderda]

Hi Jason,

to achieve what you want, we would probably have to:
 1. Rename the osgeo.org site to something like projects.osgeo.org.
 2. Set-up the Drupal site in the osgeo.org domain and have links from
    content to the project areas on the CN site.
 3. Implement shared authentication with Drupal being the master and CN
    the slave (like BEA).
Examples of such set ups are BEA Codeshare and Java.net.  However,
especially step 1 will be a labour intensive, error-prone undertaking,
depending on the amount of content on the site.  In practice, this will
be a lot of work.

Alternatively, perhaps we could look into the following: Continue to use
CN's site front page [1] as the front page and have it link into CN
project pages for specific projects and have it link into Drupal for
Drupal specific functionality.  Would that work sufficiently well, you
think?


Auke

 1. https://www.osgeo.org/

On 05 September 2006 18:38, Jason Birch wrote:
> 
> We were hoping to be able to have http://www.osgeo.org/ and
> http://osgeo.org/ answer with the content currently on
> http://community.osgeo.org/  We don't want an additional site, we want
> to replace the current main site with the Drupal content.  
> 
> My guess on this was that it would be difficult/impossible because of
> the integration of user management into the main website for all of
> the project websites, but thought I'd ask.  Ideally, the admin
> functions would go to, say, http://projects.osgeo.org/, and
> http://www.osgeo.org/ would answer with the content currently hosted
> at community, and http://osgeo.org/ would do a 301 redirect to
> http://www.osgeo.org/ (it currently goes to an SSL
> https://www.osgeo.org/)
> 
> Any WebCom folks have comments on this?
> 
> Thanks,
> Jason