Wait a sec...
No guys, we just move the www to web.aeolusproject.org
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.
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.
Estote parati (latin citation)
----- Original Message -----
From: "Matt Wagner" <matt.wagner(a)redhat.com>
To: "Jason Guiditta" <jguiditt(a)redhat.com>
Sent: Friday, October 5, 2012 5:27:36 PM
Subject: Re: How to deploy our new jekyll website
On Fri, Oct 05, 2012 at 11:19:59AM -0400, Jason Guiditta wrote:
Building on what morazi suggest above, I suggest we get going with
this and just move over to github already. We are now facing the 2
versions getting out of sync as people send pull request to the 'old'
site instead of the new jekyll stuff, so this is on its way to being a
Just the static site, you mean?
Here is what I think probably needs to happen:
1) Send an email to list saying our redmine issue tracker and wiki are
moving to $some-subdomain.aeolusproject.org, on Monday (or whatever,
as long as it is soon).
2) Back up whatever apache configs we have now
3) Switch dns and apache configs
We will have some lead time on DNS, I suspect.
I vote that we request control of DNS from Red Hat, and set up Route 53
or something. This way we can control these changes ourselves without
being at the mercy of an IT ticket queue.
I'll happily pay the ~51 cents/month for Route 53, or $29.95/year for
Dyn, if that's an issue.
Lets git 'er done!
Thanks for pushing this forward, Jay. Let's make it happen!