Adding asset compilation + Access to rails console

[jhadvig]

Asset precompilation support for Rails applications.

[jhadvig]

Will get rid of the else block and rename the asset function, also like the message difference between the docker output and builder output, but is this the template we are going to use ?

[jhadvig]

@mfojtik I have updated the PR. Pls review

[mfojtik]

looks good to me, @jwforres any thoughts about assets compilation support in the ruby base image?

[smarterclayton]

User may already have compiled their assets and not want the builder to do it for them.

[jwforres]

And I don't think we can assume that they will use asset compilation gems that require execjs

[jhadvig]

@smarterclayton, yes they may, but also they may not have the assets precompiled. In openshift 2.0 we use the disable_asset_compilation marker to disable the precompilation. Wasn't sure how to disable the precompilation in a dockerish way, cause we would need to introduce some kind of convention, which we don't want.
Any tip on that ?

@jwforres yes we can't but if the application is a rails app, in order to precompile the assets the app Gemfile needs to contains a JavaScript runtime (rubyracer, therubyrhino, ...) which will also install execjs as a dependency and so it will be located in the Gemfile.lock.
Thats why I also check in the rake_assets_precompile function that the app is a rails app.
It is similar approach like we use right now in the ruby cartridge.

[smarterclayton]

What's the state of this?

[jhadvig]

@smarterclayton The state is that it should be working, although it is quite different from the ruby-19-centos image that we provide in the openshift repository.
First we get rid of the access into the rails console with the --console flag which I introduced here.
Second we re-introduced disable_asset_compilation marker from the v2 which need to by present in my-app/.sti/markers/ folder and will prevent asset precompilation if assets are already compiled