Storage limits per-app
-
@robi the volumes can be XFS, but it requires a backing device. On a standard VPS, this means that we have to create a (big enough) file on EXT4 file system and then format it as XFS. This setup has the usual issues of loopback devices - what size this initial file should be, how to resize it live to increase/decrease storage etc. Not sure how well this performs either.
@girish yep, or do a little parted scripting first to have a device backed partition avoiding loopback issues for a more static setup..
wanna make changes? restore from remote backup.
For a more dynamic setup integrate OpenEBS/MayaData so you can keep attaching additional extent layers or do virtual migrations to different sized container attached storage mounts.
-
G girish referenced this topic on
-
G girish referenced this topic on
-
@robi the volumes can be XFS, but it requires a backing device. On a standard VPS, this means that we have to create a (big enough) file on EXT4 file system and then format it as XFS. This setup has the usual issues of loopback devices - what size this initial file should be, how to resize it live to increase/decrease storage etc. Not sure how well this performs either.
-
@Aizat No plans yet. But as a workaround, you can always do this:
- Setup a block storage of appropriate size
- Then, add it as Cloudron Volume
- Move app's data directory into the Volume
That way, the app cannot use more data than the volume itself. This does not cover databasize size which is stored outside the volume.