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
I would appreciate a feature that assists in backing up 4cat data from instances, e.g. when hosted in environments where persistent volumes are less usual. It could focus on the docker volumes, and would also be useful in scenarios where one wishes to migrate between hosts and docker-installs.
The text was updated successfully, but these errors were encountered:
I'm not sure this is something within the scope of 4CAT, if you're looking to find a way to archive or move Docker volumes; that feels like a Docker problem more than a 4CAT problem.
You can export the metadata of all datasets via the 'Dataset bulk management' page in the control panel. I suppose we could add a way to then add these to the database again. Moving the related files from their original location to the data folder of the 'new' 4CAT would then be an exercise for the reader.
Alternatively, #375 is planned to also support moving multiple datasets at once, so that could be another way to address this if it is possible to have the two 4CAT instances running simultaneously at least briefly.
I would appreciate a feature that assists in backing up 4cat data from instances, e.g. when hosted in environments where persistent volumes are less usual. It could focus on the docker volumes, and would also be useful in scenarios where one wishes to migrate between hosts and docker-installs.
The text was updated successfully, but these errors were encountered: