Like some orgs prefer to do virtual machine snapshots, some other prefer incrementala database dump, etc.
Of course I understand that (Personally is use VM snapshot by also complete DB backup in case of massive failure of my hypervirtuazation infrastructure).
In fact, from my personal experience, a lot of company didn’t make any backup (or never testing it, it’s the same thinks for me). So an easy backup process will help theses companies to use a tested backup process.
(For me a passbolt db cannot be big enough for incremental db dump)
I think before making a PR it would make sense to wait until we’re done with the cakephp 3 migration.
You want to implement this process inside a cakephp task ?
What would be nice in the meantime would be to work on a specification document. Like what should the option of such command be. Describe how we should test it, etc.
Where here can write that ?
We’re gonna launch a new help section next month, where everyone can contribute
I’m currently writting my backup creation/restoration process documentation. I will maybe put it in this new section
Yes that’s something we’d like to do in middle/long term. We don’t have the resources to work on this at the moment unfortunately.
That could be great for emergency redeploying process.
Our docker image it’s also a good way for that, mostly if you include a docker-compose (like the repo your link in your repo).
I have some question about that.
- The docker image can be use in prod now ?
- Why you didn’t include the docker-compose in your repo ?