Is your feature request related to a problem? Please describe
In one cloud, fylr containers are frequently re-created (each time we update the code in branch main of fylr). Each time /tmp is thrown away. And therefore the data of ongoing migrations is lost, which currently resides in /tmp/fylrctrl (configured in the fylr.yml hierarchy: fylr.services.backend.inspect.backup.path ).
Describe the solution you'd like:
Please make the /tmp directory of fylr instances persistent, so that it survives instance-updates (that happen e.g. to instances that are of version unstable when we commit new code to branch main ).
Describe alternatives you've considered
Other solutions would also be fine, e.g. setting the directory to outside of /tmp and then making that persistent. We chose the above request because we think it is the fastest to implement. If another solution is faster or similarly fast, fine!
The location of the "backup-manager"(in the main fylr web frontend) is separated and not the topic here.
Wish from Martin@programmfabrik: Please expose all three possible tmp configurations (main, execserver, backup)
fylr.services.backend.inspect.backup.path the most important one, this needs to be persistent across redeploys. if not configured the inspect/migration feature is not available
fylr.tempDir
fylr.services.execserver.tempDir which defaults to fylr.tempDir
Additional context:
This is about a cloud that DAM-United is operating for Programmfabrik, but the feature will be useful in other clouds, too.
If this is too specific to this one cloud, then please tell.
Is there an existing issue for this?
Is your feature request related to a problem? Please describe
In one cloud, fylr containers are frequently re-created (each time we update the code in branch main of fylr). Each time /tmp is thrown away. And therefore the data of ongoing migrations is lost, which currently resides in /tmp/fylrctrl (configured in the fylr.yml hierarchy: fylr.services.backend.inspect.backup.path ).
Describe the solution you'd like:
Please make the /tmp directory of fylr instances persistent, so that it survives instance-updates (that happen e.g. to instances that are of version unstable when we commit new code to branch main ).
Describe alternatives you've considered
Other solutions would also be fine, e.g. setting the directory to outside of /tmp and then making that persistent. We chose the above request because we think it is the fastest to implement. If another solution is faster or similarly fast, fine!
The location of the "backup-manager"(in the main fylr web frontend) is separated and not the topic here.
Wish from Martin@programmfabrik: Please expose all three possible tmp configurations (main, execserver, backup)
Additional context:
This is about a cloud that DAM-United is operating for Programmfabrik, but the feature will be useful in other clouds, too.
If this is too specific to this one cloud, then please tell.