Hello,
TL;DR: Options to mange asset dependencies are under discussion at [1]
Several of the core Foreman and Katello developers (Ohad, Walden, Daniel,
Tomas, Eric and I) have been talking about the possibility of changing the
way we handle our asset packages (js/css/etc).
We would like to open up the discussion to the community so we can get more
input and reach a decision, so I have created an RFC [1] based on our
discussions and experimentations.
The current way is with a mix of gems handled by bundler and some code
manually added under the vendor/ directory. This has some downsides which
are explained in the RFC.
Looking forward we have several options we could choose from, which are all
listed with their respective pros and cons in the RFC.
Please add your comments on the pull request and I will attempt to
incorporate everything until an agreed decision is made.
[1] https://github.com/theforeman/rfcs/pull/3
···
--
Have a nice day,
Tomer Brisker
Red Hat Engineering
Hello,
I have updated the RFC [1] with the leading option that emerged out of the
discussions so far - using NPM + Webpack to handle our assets.
Please make any comments you may still have on the RFC.
If no significant issues are raised with this choice over the next week or
so, this RFC will be considered accepted and I will start implementing the
solution based on my POC[2].
[1] https://github.com/theforeman/rfcs/pull/3
[2] https://github.com/theforeman/foreman/pull/3433
···
On Tue, May 10, 2016 at 5:26 PM, Tomer Brisker wrote:
Hello,
TL;DR: Options to mange asset dependencies are under discussion at [1]
Several of the core Foreman and Katello developers (Ohad, Walden, Daniel,
Tomas, Eric and I) have been talking about the possibility of changing the
way we handle our asset packages (js/css/etc).
We would like to open up the discussion to the community so we can get
more input and reach a decision, so I have created an RFC [1] based on our
discussions and experimentations.
The current way is with a mix of gems handled by bundler and some code
manually added under the vendor/ directory. This has some downsides which
are explained in the RFC.
Looking forward we have several options we could choose from, which are
all listed with their respective pros and cons in the RFC.
Please add your comments on the pull request and I will attempt to
incorporate everything until an agreed decision is made.
[1] https://github.com/theforeman/rfcs/pull/3
–
Have a nice day,
Tomer Brisker
Red Hat Engineering
–
Have a nice day,
Tomer Brisker
Red Hat Engineering