Currently, users with the right permissions can backup/restore either the whole site, or individual projects.
But if projects have published editions, it is not desirable that backups of projects can be restored.
Currently, backup/restore is implemented as user-triggered actions that only work in pilot mode.
So in production mode there is no danger. We'll rely on the infrastructure around Pure3D to implement a reasonable backup policy, without human intervention.
In pilot mode, the backup and restore is a convenience.
Users can save important stages of their work, try something out on top of that, and revert back if it does not work out.
Later, when it turns out desirable to have this also in production mode, we need to take care that:
backup/restore only works at the project/edition level
backup/restore is prevented for published editions
when a project with published editions is restored, those published editions will be unaffected by the restore
For now this is a non-issue, but we retain it pro memoria.
Currently, users with the right permissions can backup/restore either the whole site, or individual projects.
But if projects have published editions, it is not desirable that backups of projects can be restored.
Currently, backup/restore is implemented as user-triggered actions that only work in pilot mode.
So in production mode there is no danger. We'll rely on the infrastructure around Pure3D to implement a reasonable backup policy, without human intervention.
In pilot mode, the backup and restore is a convenience. Users can save important stages of their work, try something out on top of that, and revert back if it does not work out.
Later, when it turns out desirable to have this also in production mode, we need to take care that:
For now this is a non-issue, but we retain it pro memoria.