heroku上的Rails 5会忘记用回形针和TurboLink存储的文件：没有路径匹配_Heroku_Paperclip_Ruby On Rails 5_Turbolinks 5

heroku上的Rails 5会忘记用回形针和TurboLink存储的文件：没有路径匹配

heroku

heroku上的Rails 5会忘记用回形针和TurboLink存储的文件：没有路径匹配,heroku,paperclip,ruby-on-rails-5,turbolinks-5,Heroku,Paperclip,Ruby On Rails 5,Turbolinks 5,我有一个博客，通过回形针5.1.0和turbolinks 5.0.1上传/下载文件。没有验证的上传现在可以正常工作，但上传后下载只在短时间内有效。随后显示错误（404）： The page you were looking for doesn't exist. You may have mistyped the address or the page may have moved. If you are the application owner check the logs for mor

我有一个博客，通过回形针5.1.0和turbolinks 5.0.1上传/下载文件。没有验证的上传现在可以正常工作，但上传后下载只在短时间内有效。随后显示错误（404）：

The page you were looking for doesn't exist.

You may have mistyped the address or the page may have moved.

If you are the application owner check the logs for more information.

这无助于：

heroku rake db:migrate
heroku restart

我正在heroku上使用mysql DB进行生产。当我没有通过heroku部署时：那么本地副本在ruby 2.2.4版上就可以正常工作了

带有git push heroku master的heroku上的新部署不修复附件链接

只有手动删除数据库文件和新上传才能使附件链接在短时间内再次工作

另外，当dyno重新启动时，e。G使用heroku restart，则文件系统是新的并已删除。但我不知道如何使用redis或AmazonAWSS3使文件系统持久化

日志上写着：

2017-01-31T12:21:03.027810+00:00 heroku[路由器]：at=info method=GET path=“/system/articles/attachments/000/000/015/original/gmr-1.8.3.jar”host=infinite-taiga-25466.herokuapp.com请求id=fb775bcc-64f4-4d6b-89c0-70991af31e2f fwd=“178.15.12.47”dyno=web.1 connect=0ms服务=2ms状态=404字节=1744 2017-01-31T12:21:03.026812+00:00应用程序[web.1]：[fb775bcc-64f4-4d6b-89c0-70991af31e2f]开始获取“/system/articles/attachments/000/000/015/original/gmr-1.8.3.jar”，2017-01-31 12:21:03+0000 2017-01-31T12:21:03.027262+00:00应用程序[网站1]：[fb775bcc-64f4-4d6b-89c0-70991af31e2f] 2017-01-31T12:21:03.027284+00:00应用程序[web.1]：[fb775bcc-64f4-4d6b-89c0-70991af31e2f]操作控制器：：路由错误（没有路由匹配[GET]“/system/articles/attachments/000/000/015/original/gmr-1.8.3.jar”）： 2017-01-31T12:21:03.027302+00:00应用程序[网站1]：[fb775bcc-64f4-4d6b-89c0-70991af31e2f] 2017-01-31T12:21:03.027334+00:00应用程序[web.1]：[fb775bcc-64f4-4d6b-89c0-70991af31e2f]供应商/bundle/ruby/2.2.0/gems/actionpack-5.0.1/lib/action_调度/中间件/debug_异常 2017-01-31T12:21:03.027336+00:00应用程序[web.1]：[fb775bcc-64f4-4d6b-89c0-70991af31e2f]供应商/bundle/ruby/2.2.0/gems/actionpack-5.0.1/lib/action_调度/中间件/show_异常。rb:31:incall' 2017-01-31T12:21:03.027337+00:00应用程序[web.1]：[fb775bcc-64f4-4d6b-89c0-70991af31e2f]供应商/捆绑包/ruby/2.2.0/gems/railties-5.0.1/lib/rails/rack/logger.rb:36:in

调用应用程序'
2017-01-31T12:21:03.027338+00:00应用程序[web.1]：[fb775bcc-64f4-4d6b-89c0-70991af31e2f]供应商/捆绑包/ruby/2.2.0/gems/railties-5.0.1/lib/rails/rack/logger.rb:24:in

block-in call' 2017-01-31T12:21:03.027339+00:00应用程序[web.1]：[fb775bcc-64f4-4d6b-89c0-70991af31e2f]供应商/bundle/ruby/2.2.0/gems/activesupport-5.0.1/lib/active_support/taged_logging.rb:26:in

taged'
2017-01-31T12:21:03.027338+00:00应用程序[web.1]：[fb775bcc-64f4-4d6b-89c0-70991af31e2f]供应商/bundle/ruby/2.2.0/gems/activesupport-5.0.1/lib/active_support/taged_logging.rb:69:in

block in taged' 2017-01-31T12:21:03.027340+00:00应用程序[web.1]：[fb775bcc-64f4-4d6b-89c0-70991af31e2f]供应商/bundle/ruby/2.2.0/gems/activesupport-5.0.1/lib/active_-support/taged_-logging.rb:69:in

taged'
2017-01-31T12:21:03.027341+00:00应用程序[web.1]：[fb775bcc-64f4-4d6b-89c0-70991af31e2f]供应商/捆绑包/ruby/2.2.0/gems/railties-5.0.1/lib/rails/rack/logger.rb:24:in

call' 2017-01-31T12:21:03.027341+00:00应用程序[web.1]：[fb775bcc-64f4-4d6b-89c0-70991af31e2f]供应商/bundle/ruby/2.2.0/gems/actionpack-5.0.1/lib/action\u调度/中间件/request\u id.rb:24:in

call'
2017-01-31T12:21:03.027342+00:00应用程序[web.1]：[fb775bcc-64f4-4d6b-89c0-70991af31e2f]供应商/捆绑包/ruby/2.2.0/gems/rack-2.0.1/lib/rack/method_override.rb:22:in

call' 2017-01-31T12:21:03.027343+00:00应用程序[web.1]：[fb775bcc-64f4-4d6b-89c0-70991af31e2f]供应商/捆绑包/ruby/2.2.0/gems/rack-2.0.1/lib/rack/runtime.rb:22:in

调用
2017-01-31T12:21:03.027344+00:00应用程序[web.1]：[fb775bcc-64f4-4d6b-89c0-70991af31e2f]供应商/bundle/ruby/2.2.0/gems/activesupport-5.0.1/lib/active_-support/cache/strategy/local_-cache_-middleware.rb:28:in

call' 2017-01-31T12:21:03.027345+00:00应用程序[web.1]：[fb775bcc-64f4-4d6b-89c0-70991af31e2f]vendor/bundle/ruby/2.2.0/gems/actionpack-5.0.1/lib/action_dispatch/middleware/executor.rb:12:in

call'
2017-01-31T12:21:03.027346+00:00应用程序[web.1]：[fb775bcc-64f4-4d6b-89c0-70991af31e2f]供应商/bundle/ruby/2.2.0/gems/actionpack-5.0.1/lib/action_dispatch/middleware/static.rb:136:in

call' 2017-01-31T12:21:03.027346+00:00应用程序[web.1]：[fb775bcc-64f4-4d6b-89c0-70991af31e2f]供应商/bundle/ruby/2.2.0/gems/rack-2.0.1/lib/rack/sendfile.rb:111:in

call'
2017-01-31T12:21:03.027347+00:00应用程序[web.1]：[fb775bcc-64f4-4d6b-89c0-70991af31e2f]供应商/bundle/ruby/2.2.0/gems/railties-5.0.1/lib/rails/engine.rb:522:in

call' 2017-01-31T12:21:03.027349+00:00应用程序[web.1]：[fb775bcc-64f4-4d6b-89c0-70991af31e2f]供应商/bundle/ruby/2.2.0/gems/puma-3.7.0/lib/puma/server.rb:578:in

handle\u请求
2017-01-31T12:21:03.027349+00:00应用程序[web.1]：[fb775bcc-64f4-4d6b-89c0-70991af31e2f]供应商/bundle/ruby/2.2.0/gems/puma-3.7.0/lib/puma/server.rb:415:in

process\u客户端的 2017-01-31T12:21:03.027350+00:00应用程序[web.1]：[fb775bcc-64f4-4d6b-89c0-70991af31e2f]vendor/bundle/ruby/2.2.0/gems/puma-3.7.0/lib/puma/server.rb:275:in

block in run
2017-01-31T12:21:03.027351+00:00应用程序[web.1]：[fb775bcc-64f4-4d6b-89c0-70991af31e2f]供应商/bundle/ruby/2.2.0/gems/puma-3.7.0/lib/puma/thread_pool.rb:120:in

call' 2017-01-31T12:21:03.027352+00:00应用程序[web.1]：[fb775bcc-64f4-4d6b-89c0-70991af31e2f]vendor/bundle/ruby/2.2.0/gems/puma-3.7.0/lib/puma/thread_pool.rb:120:in

block in spawn_thread'
2017-01-31T12:21:03.027348+00:00应用程序[web.1]：[fb775bcc-64f4-4d6b-89c0-70991af31e2f]供应商/捆绑包/ruby/2.2.0/gems/puma-3.7.0/lib/puma/configuration.rb:226:in

call'

C:\Sites\blog\u production\u heroku>

这是根本原因：当dyno定期重新启动或使用heroku restart重新启动时，文件系统

#Paperclip
gem 'paperclip', git: 'git://github.com/thoughtbot/paperclip.git'