----- 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, > >> > > >> > We (me and Mike Orazi) faced a "tiny" issue with the opportunity > >> > to get hosted by github with pages. > >> > > >> > The problem is that at the moment we have this setup: > >> > > >> > An apache server with mod_proxy that : > >> > > >> > on / : will return our website with nanoc > >> > on /redmine : will redirect to our thin server with Redmine > >> > > >> > Now, if we get hosted by github we will not have anymore > >> > /redmine that will be redirected on redmine instance. > >> > > >> > So we faced three possible ways: > >> > > >> > 1) Keep the current machine and have the git-hook that will care > >> > about re-run jekyll and build the files) > >> > > >> > 2) Create a subdomain called web.aeolusproject.org for github > >> > pages > >> > and our mod_proxy will just redirect us there > >> > >> Hmmm, this one sounds like the best option to me. > >> > >> * seems easy to implement. :) > >> * no broken links for the Redmine content. Everything still > >> works. > >> * Easy to wind back if things don't work right. > >> > >> + Justin > >> > > > >I think we probably want more details this solution. In particular, > >I'm thinking: > >- what do the current Rewrite & Proxy rules look like? -- in > >particular, I think we do some amount of Rewriting to move > >everything over to ssl, which we likely want to keep for redmine, > >but potentially drop for github. > >- what else is running on the box that we need to think about w/r/t > >Rewrite/Proxy stuff? > >- what will the next set of apache rules look like? > >- how would we test this? (should be simple, but let's be explicit) > >- how do we roll back if we make a mistake? (presumably it will be > >make sure we keep the old rules around, put them back in place, > >restart apache but it is worthwhile to think it through to make > >sure we haven't missed anything) > > > >m > > > >> > >> > 3) Create a subdomain called issues.aeolusproject.org for > >> > redmine > >> > and have all the issues mapped there and the website on github > >> > (This mean we gonna loose all the link to previous issues) > >> > > >> > > >> > Looking forward to get your feedback on this, > >> > > >> > Cheers, > >> > - Francesco > >> > >> -- > >> Aeolus Community Manager > >> http://www.aeolusproject.org > >> > >> > > 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 > problem. 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 > 4) Profit. > > Lets git 'er done! > > -j >
+1
