Bug 1470816 - rails apps should have RAILS_SERVE_STATIC_FILES set by default
rails apps should have RAILS_SERVE_STATIC_FILES set by default
Product: Red Hat Software Collections
Classification: Red Hat
Component: rh-ruby23-docker (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: 3.2
Assigned To: Pavel Valena
BaseOS QE - Apps
Depends On:
  Show dependency treegraph
Reported: 2017-07-13 14:08 EDT by Aleksandar Kostadinov
Modified: 2018-02-28 06:07 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Aleksandar Kostadinov 2017-07-13 14:08:05 EDT
Description of problem:
When a rails app is created, the default mode is `production`. In production mode, the app by default does not serve static files like the compiled assets.

To make rails app work OOB, we need to set as detault the RAILS_SERVE_STATIC_FILES env variable to the worker pod.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
I guess any app will do the job but you could try https://github.com/openshift-qe/ownthat

1. oc create -f openshift/secret.yml # first edit the file
2. oc process -f openshift/template.yml | oc create -f -
3. open app in browser

Actual results:
styles and other assets missing, page looking really ugly

Expected results:
page looks nice and assets are served to browser

Note You need to log in before you can comment on or make changes to this bug.