How to deploy our new jekyll website
by Francesco Vollero
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
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
11 years, 5 months
Re: How to deploy our new jekyll website
by Hugh O. Brock
On Thu, Sep 27, 2012 at 11:19:34AM +1000, Justin Clift wrote:
> Note - I've removed aeolus-devel from this, because I'm including
> links to internal things.
>
>
> On 27/09/2012, at 3:23 AM, Hugh Brock wrote:
> <snip>
> > I have a radical suggestion I would like to throw out for comment:
> >
> > I was talking to Matt Hicks the other day, of OpenShift, and he claims
> > they are moving *their entire agile setup* to GitHub. Basically they're
> > going to ditch stories in Rally and move them to the GitHub issue
> > tracker instead.
>
> Interesting. As a data point, saw this last night in their recent archives
> while trying to resolve a problem:
[snipped private link]
>
>
> Gives the impression that their GitHub usage varies heaps, which doesn't
> feel in line with a group moving everything to it.
>
I'm just relaying what I heard from Matt Hicks, who is the engineering
lead for OpenShift. I don't think the switch is planned to happen
overnight, but they are heavy users of Rally now, and they are finding
that straddling two tools is bringing more problems than it solves.
But, leaving that aside, what do you guys think about the idea for
Aeolus? I know Redmine has more tracking features than GitHub, but it
feels like we're saddling ourselves with a substantial burden (hosting
an app, manually closing issues after committing code, etc.) that we
could erase simply by moving story tracking to GitHub.
--Hugh
--
== Hugh Brock, hbrock(a)redhat.com ==
== Engineering Manager, Cloud BU ==
== Aeolus Project: Manage virtual infrastructure across clouds. ==
== http://aeolusproject.org ==
"I know that you believe you understand what you think I said, but I’m
not sure you realize that what you heard is not what I meant."
--Robert McCloskey
11 years, 5 months
[PATCH 0/1 conductor] BZ860715 - translation missing in the provider account creation page
by Tzu-Mainn Chen
This error comes about because some systems seem to have credential labels with the first letter capitalized, rather than being all lowercase. To duplicate the issue, update the labels in the credential_definitions table.
I'm not entirely sure whether labels should or should not be capitalized, but for upgrade purposes, I think we have to assume that some may be; so my solution is just to downcase the key string.
Mainn
11 years, 5 months
[aeolus-incubator/image-management-engine] ded215: Allow custom partials in resource views
by Martyn Taylor
Branch: refs/heads/master
Home: https://github.com/aeolus-incubator/image-management-engine
Commit: ded2157388af892e5a0ae291266437ae6c39cd4c
https://github.com/aeolus-incubator/image-management-engine/commit/ded215...
Author: Martyn Taylor <mtaylor(a)redhat.com>
Date: 2012-09-28 (Fri, 28 Sep 2012)
Changed paths:
M app/views/image_management/base_images/_base_image.xml.haml
M app/views/image_management/image_versions/_image_version.xml.haml
M app/views/image_management/provider_images/_provider_image.xml.haml
M app/views/image_management/target_images/_target_image.xml.haml
M app/views/image_management/templates/_template.xml.haml
M spec/controllers/base_images_controller_spec.rb
M spec/controllers/image_versions_controller_spec.rb
M spec/controllers/provider_images_controller_spec.rb
M spec/controllers/target_images_controller_spec.rb
M spec/controllers/templates_controller_spec.rb
A spec/views/base_images_spec.rb
A spec/views/image_versions_spec.rb
A spec/views/provider_images_spec.rb
A spec/views/target_images_spec.rb
A spec/views/templates_spec.rb
A test/dummy/app/views/image_management/base_images/_custom.xml.haml
A test/dummy/app/views/image_management/image_versions/_custom.xml.haml
A test/dummy/app/views/image_management/provider_images/_custom.xml.haml
A test/dummy/app/views/image_management/target_images/_custom.xml.haml
A test/dummy/app/views/image_management/templates/_custom.xml.haml
Log Message:
-----------
Allow custom partials in resource views
Signed-off-by: Jason Guiditta <jguiditt(a)redhat.com>
11 years, 5 months