Building standalone backup web interface

[gubuntu]

We plan to provide a standalone backup web interface so users can interact with backup and restore processes through the web front-end.

Implementation choices depend on the input from Alessio and the GeoNode community in https://github.com/kartoza/docker-geosafe/issues/121

child of #458

[gubuntu]

You've implemented this right, @lucernae ? moving to testing

[NyakudyaA]

@lucernae what does the backup section in the web do. Is this working. It is unclear to a user what is happening here. Are we supposed to be using the web or the management command?. The ticket refers to the web

[lucernae]

We haven't built standalone backup web interface. This ticket refer to a system of web interface where we manage the backup files through this interface. This interface needs to be separated from the system that needs to be backed up. If it is manages GeoNode's backup, then it needs to be separated from GeoNode (thus we named it standalone) and uses it's own internal database.

This ticket should be in the backlog.

The one that I managed to fix is GeoNode's internal backup admin page. The one that you access from Admin page. However, I think it is very buggy by design. For example, you are not supposed to execute backup/restore command from within the same post action of the web. If the process takes a long time, it will be killed by nginx. You have to delegate the action to a celery worker or another separate thread and manage the state. But this system was not implemented currently. I fixed the management command and the web interface, however for the web interface, if it takes a long time and the process killed by nginx, there's nothing I can do with that bad UX. I recommend the management command.

cc @gubuntu @NyakudyaA

[lucernae]

The related ticket that supposed to be tested is this: https://github.com/kartoza/docker-geosafe/issues/121

[NyakudyaA]

Ok @lucernae cc @gubuntu I will move this to the backlog and test the management commands