Yeah sorry just confused the modules, was mod_rewrite.
-FV
----- Original Message -----
From: "Matt Wagner" <matt.wagner(a)redhat.com>
To: "Francesco Vollero" <fvollero(a)redhat.com>
Cc: aeolus-devel(a)lists.fedorahosted.org, "Jason Guiditta"
<jguiditt(a)redhat.com>
Sent: Friday, October 5, 2012 7:57:54 PM
Subject: Re: How to deploy our new jekyll website
On Fri, Oct 05, 2012 at 01:41:15PM -0400, Francesco Vollero wrote:
Wait a sec...
No guys, we just move the www to
web.aeolusproject.org that gonna
be redirected to github pages via mod_proxy I am going to do some
testings this weekend in order to be 100% sure that the idea work.
This would work, but what is the advantage? This would require us to
maintain a webserver forever, even if it did nothing but redirect to
other services. Doesn't it make more sense to move components apart so
that they can stand on their own?
What Jay required would let the GitHub Pages site stand on its own, at
a normal "www" domain. And it would separate Redmine onto a subdomain so
we can manage it separately, like if we want to move it to OpenShift
some day, or to some hosted service, etc.
If we don't go with that approach, isn't this a one-liner with
mod_rewrite, which we already have in our HTTP config? mod_proxy seems a
bit extravagant.
Anyway, the migration should not "touch" our redmine
instance but
anything will be saved before _any_ modify on the et3 machine.
Before actually migrating to gh-pages we need to put in sync
the pages properly.
Are the pages on the jekyll branch not up-to-date?
-- Matt