Remove the need of backup/ symlink and 0644 permissions on backup archives.
Backup archives can’t be world-readable because they may contain sensitive informations. You could isolate privileged operations into some scripts, as you already did, and call them with sudo.
I think the latest PKI - Server certificate page is very similar to this module and could be an example of how to arrange the things:
Hi Davide,
I agree with you on enforcing the auth on http requests.
On the second point (removing the need for backup/ symlink), I can see the functions to obtain the list of backups but I do not see how you can download the files after that since there will not be a function that will be able to read the file to put it to the header buffer…
So, List / Delete archives, will be possible, but i can’t see the mechanism for download. I’ve mentioned this before, that i can’t make this feature available…
Do you have a possible way to achieve this ?
I agree Davide, it looks like the best solution and it will also keep the same “profile” as the rest of the NS code.
This starts to look very promising!
I’ll try to take a look at the section of code for getting the file into the view.
I still don’t get how the function will get triggered when you click the download button…
@Davide,
I’ve installed the Backup History module you provided and i have encountered two issues:
1 After a backup is made (or a backup is deleted) , on the History tab i see the table for 1 second then it gets replaced by this:
Sure Davide, I’ on for how this module can be improved.
I think that we can remove the tabs Backup and Restore and keep only one that will have the Backup and Restore functions alongside the table of backups. (they are kind of redundant in my opinion)
As I have said, I’ll try to take a look at the code you provided as reference and figure it out if I can.
This way I can help you on porting all this to the more standard NS code
I agree, they are kinda redundant and we could arrange the whole UI in a cleaner way, too. But I must keep into account the Enterprise module that - as said above - already provides a similar feature. I need some time to iron out the kinks, please be (still) patient!
Meanwhile, we can safely proceed with this add-on!
Well i certainly use it if for example i know that a certain backup contains bad data or i have issues with it when i try to restore it.
I will remove it just so I or somebody else will not try to restore it from mistake.
If a connection is not available, the restore procedure cannot reinstall original modules. I’d like to add a “TODO” message that appears if the restored system lacks of originally installed modules. Say
The message disappears when the first configuration backup has completed or all missing modules are installed.