Handle Rails 404, 422 and 500.html

[davidjrice]

Handle the default Rails error pages and also upload to the storage bucket.

Additionally, investigate integration with heroku custom error pages and automatically setting the ENV vars to the new locations. http://devcenter.heroku.com/articles/custom_error_pages

[taylorbrooks]

Is this working? Will asset_sync pull in custom 404 and 500 pages?

Any settings that should be configured in the yml file needed?

I didn't see the default error pages in my S3 bucket.

[courtsimas]

+1

[juandazapata]

+1

[reconbot]

This sort of falls under /public folder syncing. Which I also consider important. I think it would be nice to do it, even if it was a separate rake task.

[nneal]

+1

[hadees]

any update?

[dashbitla]

Is anyone solved this problem? I dont see the error pages synced to S3 from public folder, would like to know how its been solved!

One thing that I see is -move these error pages to assets/ folder and change the routes.rb to point to that.

We can probably use one of these approaches for customer error pages ...
https://mattbrictson.com/dynamic-rails-error-pages
https://github.com/mirego/gaffe

Any thoughts?