[katello-devel] Help! How to turn a production install into development?
Ivan Nečas
inecas at redhat.com
Thu Oct 11 21:07:23 UTC 2012
On 10/11/2012 08:19 PM, Tom McKay wrote:
>
> ----- Original Message -----
>> From: "Tom McKay" <thomasmckay at redhat.com>
>> To: "Miroslav Suchy" <msuchy at redhat.com>
>> Cc: katello-devel at redhat.com
>> Sent: Thursday, October 11, 2012 2:06:07 PM
>> Subject: Re: [katello-devel] Help! How to turn a production install into development?
>>
>>
>>
>> ----- Original Message -----
>>> From: "Miroslav Suchy" <msuchy at redhat.com>
>>> To: katello-devel at redhat.com
>>> Sent: Thursday, October 11, 2012 12:54:47 PM
>>> Subject: Re: [katello-devel] Help! How to turn a production install
>>> into development?
>>>
>>> On 11.10.2012 18:32, Tom McKay wrote:
>>>> then requires redcarpet gem, which I can't seem to
>>>> find/install.
>>> yum install rubygem-redcarpet
>>>
>>> http://koji.fedoraproject.org/koji/packageinfo?packageID=13835
>>>
>>> Mirek
>>>
>>> _______________________________________________
>>> katello-devel mailing list
>>> katello-devel at redhat.com
>>> https://www.redhat.com/mailman/listinfo/katello-devel
>>>
>> Since this is the only missing gem that prevents switching from
>> production to development, can we please include it with the
>> production RPMs? It will be important to easily let support people
>> switch a customer's install to increase debug logging.
> I just saw /etc/sysconfig/katello KATELLO_LOGGING so switching to development isn't needed. (Still would vote to include redcarpet if that's the only missing gem.)
Yop, switching to development mode just to increase logging is a bit
overkill. I also wouldn't say it's the only gem missing. Just take a
look at the Gemfile and all the gems under @@@DEV_ONLY@@@. Many of them
are just for running tests, but still. Development mode = begin able to
develop. Production machine should never be run in development mode,
because it's not the way it should be used. And I'm quite happy that the
missing gem causes that to fall before it causes more harm.
>
> I didn't see a flag in katello-configure to change this value; worth adding?
Since we now support rerunning katello-configure more times, this is
good point. I vote for it, if there is not something that would cause
trouble.
-- Ivan
>
>> Thanks!
>>
>> _______________________________________________
>> katello-devel mailing list
>> katello-devel at redhat.com
>> https://www.redhat.com/mailman/listinfo/katello-devel
>>
> _______________________________________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/katello-devel
--
Ivan
More information about the katello-devel
mailing list