You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, none of the static assets (images, javascript, css, etc) will be served by a Kuby-deployed application, at least not by default. This is because Rails disables serving static assets in production. You can enable it by setting config.public_file_server.enabled = true in config/environments/production.rb, or by setting the RAILS_SERVE_STATIC_FILES environment variable.
Kuby-deployed apps should serve static assets out of the box. We can do one of:
set the aforementioned environment variable.
build assets into a separate Docker image along with a simple file server. Much more complicated.
The text was updated successfully, but these errors were encountered:
Currently, none of the static assets (images, javascript, css, etc) will be served by a Kuby-deployed application, at least not by default. This is because Rails disables serving static assets in production. You can enable it by setting
config.public_file_server.enabled = true
in config/environments/production.rb, or by setting theRAILS_SERVE_STATIC_FILES
environment variable.Kuby-deployed apps should serve static assets out of the box. We can do one of:
The text was updated successfully, but these errors were encountered: