[katello-devel] bundler woes....

[Dmitri Dolguikh]

On 06/11/12 09:06 AM, Lukas Zapletal wrote:
> On Mon, Nov 05, 2012 at 08:08:05PM -0500, Justin Sherrill wrote:
>> 1) After reading through some of the previous bundler discussions, I
>> found this PR: https://github.com/Katello/katello/pull/526/files
>>
>> This doesn't seem to be integrated into our build process at all
>> though?    Is there any plan on doing that? This seems to be what
>> aeolus is doing and is probably the way to go.
>>
>> Other possible solutions (that i'm not as big of a fan of):
>>
>> 2) Use two gemfile files (one for production deployment and one for
>> testing/development)
>>
>> 3) Use the f16/f17/rhel6 gem files and have some process to keep
>> them up to date.
> Other option could be to:
>
> a) Get rid of Bundler in the production mode. Aeolus has already a
> little plugin for that, I think Petr evaluated it and it works.
> Technically we need to add one or two Ruby files and change few lines,
> but it would be best to ask Aeolus to create a rubygem from it, so we
> can share the code. (*)
+1 to that one as well. (although this is not going to help with 
resolving the issue Justin is talking about).
-d
>
> b) Create an environmental variable like DEVELOPMENT_MODE=1 and in our
> Gemfile put all the development gems there
>
> c) Katello-devel post script could only set this variable in
> /etc/sysconfig/katello directory using sed. Or it can just drop a file
> which we will include somewhere (like conf.d directories do). Or we can
> also leave this only on user (to switch it on).
>
> With this, you will be able to:
>
> A) Start production server with development gems
>
> B) Start the server from the command line (setting the variable).
>
> C) Finally get rid of Bundler (*)
>
> (*) - it seems these steps are optional, it should work also with
> Bundler but it will be creating those lock files, it could be better
> without it
>