blocks|key|156833|text|Heroku的文件系统是只读的。您不能期望上传的任何内容都会在那里持久存在，您需要使用外部存储机制，比如亚马逊的S3。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|156834|有关详细信息，请参阅链接。|156835|https://devcenter.heroku.com/articles/s3+https://devcenter.heroku.com/articles/dynos#isolation-and-security|offset|length|156836|entityMap|0|LINK|mutability|MUTABLE|url|https://devcenter.heroku.com/articles/s3|1|https://devcenter.heroku.com/articles/dynos#isolation-and-security^0|0|0|0|14|0|15|1U|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$F|U|G|V|1|W]|$F|X|G|Y|1|Z]]|A|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]|P|$5|K|L|M|A|$N|Q]]]]

Heroku's filesystem is readonly. You can't expect anything you upload to persist there, you need to use an external storage mechanism, something like Amazon's S3 for example.

See the links for more details.

<a href="https://devcenter.heroku.com/articles/s3" rel="nofollow">https://devcenter.heroku.com/articles/s3</a>
<a href="https://devcenter.heroku.com/articles/dynos#isolation-and-security" rel="nofollow">https://devcenter.heroku.com/articles/dynos#isolation-and-security</a>

blocks|key|2286391|text|Heroku实例运行的文件系统不是只读的，但它是短暂的，也就是说，在重新启动实例之后，存储在那里的文件不会持久存在。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2286392|这是Heroku深思熟虑的设计决定，它迫使您考虑存储数据的位置以及它对可伸缩性的影响。|2286393|你在问数字海洋-我没有使用它们，但是我从你的问题中假设它们允许你存储到一个持久的本地文件系统中。|2286394|接下来你必须问的问题是:如果你想运行你的应用程序的多个实例，会发生什么？它们是否共享相同的持久文件系统？他们能访问对方的文件吗？当几个应用程序实例使用相同的文件系统时，如何处理文件锁定以避免竞争条件？|2286395|Heroku的模型迫使您要么把东西放到数据库中，要么使用外部服务存储它。通常，任何这类系统都具有合理的可伸缩性--您可以有多个Heroku实例(可能运行在不同的机器、不同的数据中心等上)，并且它们都会很好地交互。|2286396|我确实同意，对于一个简单的用例--你只想在开发过程中运行一个应用程序的一个实例--这可能不方便，但我认为这是它背后的原因--强迫你设计这类东西，而不是假设它可以在本地存储所有东西，然后发现你需要完全重新设计才能使它具有可伸缩性。|2286397|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

The filesystem that your Heroku instance runs on is not read-only, but it is transient - i.e. files that you store there will not persist after an instance restart.

This is a deliberate design decision by Heroku, to force you to think about where you store your data and how it impacts on scalability.

You're asking about Digital Ocean - I haven't used them but I assume from your question that they allow you to store to a persistent local filesystem.

The question that you then have to ask is: what happens if you want to run more than one instance of your app? Do they share the same persistent filesystem? Can they access each other's files? How do you handle file locking to avoid race-conditions when several app instances are using the same filesystem?

Heroku's model forces you to either put stuff in a database or store it using some external service. Generally, any of these sorts of systems will be reasonably scalable - you can have multiple Heroku instances (perhaps running on different machines, different data-centers, etc), and they will all interact nicely.

I do agree that for a simple use-case where you just want to run a single instance of an app during development it can be inconvenient, but I think this is the reasoning behind it - to force you to design this sort of thing in, rather than developing your whole app on the assumption that it can store everything locally and then find out later that you need to completely redesign to make it scalable.

blocks|key|157928|text|你现在看到的是赫洛库的ephemeral+file+system：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|157929|每个dyno都有自己的ephemeral+filesystem，有一个最新部署的代码的新副本。在dyno的生命周期中，它正在运行的进程可以使用文件系统作为临时的便签，但是任何其他dyno中的进程都看不到写入的文件，并且在dyno停止或重新启动时，写入的任何文件都将被丢弃。|blockquote|BOLD|157930|简而言之，这意味着您上传的任何文件只会持续到dyno运行的时间。当dyno关闭时，文件将被删除，除非它们是local+git的一部分。|157931|解决这个问题的方法是将文件存储在第三方服务(通常是S3+)上。这将把文件存储在一个独立于Heroku的系统上。|157932|Paperclip和Carrierwave都支持S3+(简单存储服务)--通过一个名为fog的gem。S3为您提供了一个“自由”层，允许您免费存储一定数量的数据(我已经忘记了)。|157933|我强烈建议设置一个S3帐户，并将其链接到您的Heroku应用程序。这样，您上传的任何文件都将被存储在场外.|157934|entityMap|0|LINK|mutability|MUTABLE|url|https://devcenter.heroku.com/articles/dynos#ephemeral-filesystem|1|https://github.com/carrierwaveuploader/carrierwave#using-amazon-s3|2|https://github.com/thoughtbot/paperclip/wiki/Paperclip-with-Amazon-S3|3|4|http://fog.io/|5|https://aws.amazon.com/s3/pricing/^0|B|L|B|L|0|0|B|K|3D|F|0|0|1V|1H|5|0|0|1J|P|2|P|2|1|0|0|2H|0|9|A|B|17|3|0|9|2|A|B|3|17|3|4|1O|5|5|0|0|1H|0^^$0|@$1|2|3|4|5|6|7|18|8|@$9|19|A|1A|B|C]]|D|@$9|1B|A|1C|1|1D]]|E|$]]|$1|F|3|G|5|H|7|1E|8|@$9|1F|A|1G|B|C]|$9|1H|A|1I|B|I]]|D|@]|E|$]]|$1|J|3|K|5|6|7|1J|8|@$9|1K|A|1L|B|I]|$9|1M|A|1N|B|C]]|D|@]|E|$]]|$1|L|3|M|5|6|7|1O|8|@$9|1P|A|1Q|B|I]|$9|1R|A|1S|B|C]]|D|@$9|1T|A|1U|1|1V]]|E|$]]|$1|N|3|O|5|6|7|1W|8|@$9|1X|A|1Y|B|I]|$9|1Z|A|20|B|C]|$9|21|A|22|B|C]|$9|23|A|24|B|C]]|D|@$9|25|A|26|1|27]|$9|28|A|29|1|2A]|$9|2B|A|2C|1|2D]|$9|2E|A|2F|1|2G]]|E|$]]|$1|P|3|Q|5|6|7|2H|8|@$9|2I|A|2J|B|I]]|D|@]|E|$]]|$1|R|3|-4|5|6|7|2K|8|@]|D|@]|E|$]]]|S|$T|$5|U|V|W|E|$X|Y]]|Z|$5|U|V|W|E|$X|10]]|11|$5|U|V|W|E|$X|12]]|13|$5|U|V|W|E|$X|10]]|14|$5|U|V|W|E|$X|15]]|16|$5|U|V|W|E|$X|17]]]]

What you're looking at is something called the <a href="https://devcenter.heroku.com/articles/dynos#ephemeral-filesystem" rel="nofollow"><code>ephemeral file system</code></a> in Heroku:

<blockquote>
 Each dyno gets its own <code>ephemeral filesystem</code>, with a fresh copy of the most recently deployed code. During the dyno’s lifetime its running processes can use the filesystem as a temporary scratchpad, but no files that are written are visible to processes in any other dyno and any files written will be discarded the moment the dyno is stopped or restarted
</blockquote>

In short, it means that any files you upload will only last for the time the dyno is running. When the dyno shuts down, the files will be removed unless they were part of the <code>local</code> git repo.

<hr>

The way to resolve the issue is to store the files on a third-party service - typically <a href="https://github.com/carrierwaveuploader/carrierwave#using-amazon-s3" rel="nofollow"><code>S3</code></a>. This will store the files on a system independent of Heroku.

Both <a href="https://github.com/thoughtbot/paperclip/wiki/Paperclip-with-Amazon-S3" rel="nofollow"><code>Paperclip</code></a> &amp; <a href="https://github.com/carrierwaveuploader/carrierwave#using-amazon-s3" rel="nofollow"><code>Carrierwave</code></a> support S3 (Simple Storage Service) - through a gem called <a href="http://fog.io/" rel="nofollow"><code>fog</code></a>. S3 gives you a <a href="https://aws.amazon.com/s3/pricing/" rel="nofollow">"free" tier</a>, allowing you to store a certain amount of data (I've forgotten how much) for free.

I would strongly recommend setting up an S3 account and linking it to your Heroku app. This way, any files you upload will be stored off-site.

I saw this question:<a href="https://stackoverflow.com/questions/11246736/after-git-push-heroku-uploaded-files-on-heroku-are-lost">After git push heroku - uploaded files on Heroku are lost</a>

<blockquote>
 each time the application shuts down and restarts after being inactive
 for x minutes), your application is recreated and all stored data is
 lost.(C)
</blockquote>

Right now I have user which can upload two photos.I got email confirmation of new users. So I can check that user registered and uploaded photo 4 and 14 hours ago.
I've made my last commit and pushed it to heroku around 19 hours ago. And this 4 images, that new users uploaded are lost now.But I can see images if I just now register the user. So it seems to be really true that my app was inactive for x minutes and then it restarts and deletes images.

I read some questions like this <a href="https://stackoverflow.com/questions/13597837/rails-images-erased-after-a-new-commit-on-heroku">Rails] Images erased after a new commit on heroku</a>
There it says that I should use external server like aws s3( I have no idea what it is and how much it will cost and how to connect it)
So is it really true? what are my other options? may be I should simply use digital ocean(won't be there the same problem?) or something else. Will this problem continue in paid account?

I use rails and upload files using carrierwave gem, I can't upload code here cause I am writing from another laptop.

Heroku erases images each time the application shuts down and restarts after being inactive for x minutes?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我看到了这个问题：每次应用程序关闭并在不活动x分钟后重新启动时，您的应用程序都会被重新创建，并且所有存储的数据都会丢失。现在我有用户可以上传两张照片，我收到了新用户的电子邮件确认。所以我可以检查用户注册和上传照片4和14小时前。我做了最后一次承诺，并在19小时前把它推给了heroku。而这4张图片，上传的新用户都是丢失...

问每次应用程序关闭并在不活动x分钟后重新启动时，Heroku都会擦除图像？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问每次应用程序关闭并在不活动x分钟后重新启动时，Heroku都会擦除图像？EN