Cloudron Forum

I use a nfs target for backups. and sometimes i have to restart some servers or routers or vpn. and even sometimes after this the backup volume is not mounted.

then the next backup fails. and the only thing i have to do is to click "remount storage" one time, 1 second later the mountpoint is green again and then i can manually start a new backup or wait for the automatic one.

it would be nice, if the backup task clicks the remount storage button for me

i am not sure if this is a feature request or a bug report

Yesterday i had to restore my synapse server from backup. worked.

but: only the database was broken. the restore of the database runs some seconds and all is fine. after this i had to wait one and a half hour while the media data (files on filesystem) where restored. my problem: only the database was broken. to solve my primary problem, the one minute restore of the database has could been the solution.

i would prefer to select in a advanced tab, which parts of my backup should be restored. the same thing as with nextcloud or wordpress or other tools.

It would be a nice feature to make a decision if an app uses the central database or its own container. in my docker-compose stacks i mostly have single purpose database containers for services like synapse. it is a question of taste, but i like single purpose database containers more than centralized storage.

There are Apps, where it makes no sense to run a dedicated Database Server. But on Things like Synapse or Mastodon it makes sense to split it from other Apps. Even in case of need for performing tweaks.

Hi,

it would be nice to enable short-lived ReadWrite access for container images, especially for quick and dirty hacks and fixes.

For example: In the last Synapse update, there was a bug using version x of Pillow where a deprecated attribute (Image.ANTIALIAS) was gone. This made it impossible to upload images to Matrix. Changing a line of code or installing PIL in version y could solve the problem. But not in the ReadOnly container.

I would like to see a button "Enable RW in container until restart" for non-persistent changes/fixes/debugging/something else.

A short reminder that all changes are lost on restart would be helpful.

@holm

the named app b1f26524-5ea6-43a0-bcd7-da77b20fb136 is a disabled gitlab instance.

@girish

thank you for the fast help! the system is up and running again!