How to deploy our new jekyll website

Francesco Vollero fvollero at redhat.com
Fri Oct 5 21:10:08 UTC 2012


On Sat, Oct 06, 2012 at 06:28:23AM +1000, Justin Clift wrote:
> On 06/10/2012, at 1:25 AM, Michael Orazi wrote:
> > ----- Original Message -----
> >> On 25/09/12 15:24 -0400, Michael Orazi wrote:
> >>> ----- Original Message -----
> >>>> On 26/09/2012, at 1:19 AM, Francesco Vollero wrote:
> >>>>> Hi everyone,
> >>>>> 

[snip]

> 
> Heh, the old site repo is what's really still being used.  We need to pull
> the new content across to the jekyll repo, deprecate the old site repo,
> then and update our processes to use the new jekyll version.
> (me especially)
> 
> I'd been kind of thinking we'd do the GitHub www move at the same time,
> but since that's kind of up in the air due to our wider GitHub
> considerations, we could just start using jekyll for the site now.
>

We can also do something more easy...we start the migration to jekyll adding
the updates that are missing atm but we didn't yet add the CNAME so since the
repos will be in sync when we gonna do the CNAME migration everything should
go smooth.

> 
> + Justin
> 
> --
> Aeolus Community Manager
> http://www.aeolusproject.org
> 



More information about the aeolus-devel mailing list