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
{{ message }}
This repository has been archived by the owner on Sep 4, 2021. It is now read-only.
How does Flynn manage stateful applications like Wordpress that rely on local data storage for plugins/caches/uploads? What process, if any, does Flynn use to help keep that data in sync?
The text was updated successfully, but these errors were encountered:
Flynn currently supports adding ZFS volumes to your applications which means data saved to the volume will be persisted even if the job dies, but these volumes are not currently sticky, so whilst the data remains on disk, restarting your app will get a new, empty volume. This will be fixed by our v2 scheduler.
As for keeping data in sync between multiple jobs, it is not currently supported out of the box but we have an issue tracking adding NFS support.
How does Flynn manage stateful applications like Wordpress that rely on local data storage for plugins/caches/uploads? What process, if any, does Flynn use to help keep that data in sync?
The text was updated successfully, but these errors were encountered: