would it be possible to move towards using omnibus packing for theforeman?
i would love it if TF was self-contained with its own ruby and gems in
/opt/foreman much like chef/sensu/etc do.
i have newer system-ruby on my machines than theforeman requires, so
self-containing all the deps seems like
At the very least support both. This is a point release and this is a
pretty major change for a non-major release.
As per the comment from Ewoud the bulk of people who will use this use it
in ERB and templates. The templates being probably the easiest to 'fix'.
Personally, keeping this permanen
On Wed, 2017-04-19 at 14:10 +0300, Tomer Brisker wrote:
> Since it seems there wasn't an agreement on reverting this made in
> time for 1.15, I'd say we should support both for now and reconsider
> in the future pending a rewrite of the template engine using a proxy
> object as we discussed.
+1, s
Since it seems there wasn't an agreement on reverting this made in time for
1.15, I'd say we should support both for now and reconsider in the future
pending a rewrite of the template engine using a proxy object as we
discussed.
On Tue, Apr 18, 2017 at 10:15 AM, Marek Hulán wrote:
> On pondělí 1
