Add Persistent Filesystems for Deployments

Describe your feature request
Add persistent filesystems for deployments.

What problem(s) would this feature solve?
Currently with the beta hosting you can run pretty much anything on Replit. Deployments not having persistent filesystems limits the projects possible with Replit. I have consulted with 9pfs and the following really cool projects that work with the beta hosting will not work with Deployments:

  • Discourse
  • Dendrite (Matrix server)
  • NoVNC VMs

9pfs has gotten these things working with the beta hosting and they are really cool projects showcasing the power of Replit and also the knowledge of the person creating these projects. We all know that the beta hosting will end sooner or later, and I don’t want projects like these to end with them. Non-persistent filesystems greatly hinder one’s ability to freely use Replit for any kind of project.

Explain what you were trying to do when you came across the problem leading to this feature request
I wasn’t doing anything per-say, just reading and learning and thinking about Replit and its features and future.


I also have multiple personal projects that require persistent filesystem which is why I’m still using always on repls

4 Likes is forcing us to use Deployment.
I’m ok to pay to have things hosted correctly, but without persistent filesystem it is really more complicated and almost useless for me to deploy. All the dockers or pods I can see in work allow to connect to persistent filesystem and that’s not an issue … With Repl, relying only on databases for everything is absolutely blocking the expansion of Deployments. I can’t understand how the fact persistent filesystems don’t exist in deployment is only a small line in the end of the Migration guide. All new happy users of migrating will face this problem.


Not only do Deployments not have persistent filesystems, but Docker doesn’t work on Replit.