How to deploy our new jekyll website

Justin Clift jclift at redhat.com
Tue Oct 9 09:46:22 UTC 2012


On 06/10/2012, at 7:10 AM, Francesco Vollero wrote:
> On Sat, Oct 06, 2012 at 06:28:23AM +1000, Justin Clift wrote:
<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.

Heh, yeah, that's pretty much what I was meaning.

Just added the missing files from the old repo (static
redmine, source images, etc) and started converting over the
news items from the original site.

Guess we should start using pull requests for the Jekyll
site repo, instead of just automatically pushing everything?

(btw, please kill off the old repo, it's confusing to have)

+ Justin

--
Aeolus Community Manager
http://www.aeolusproject.org




More information about the aeolus-devel mailing list