Skip to content
This repository has been archived by the owner on Feb 20, 2024. It is now read-only.

Having a getter for ProcessorManager #94

Open
chesedo opened this issue Nov 10, 2015 · 2 comments
Open

Having a getter for ProcessorManager #94

chesedo opened this issue Nov 10, 2015 · 2 comments
Milestone

Comments

@chesedo
Copy link
Contributor

chesedo commented Nov 10, 2015

Note this issue related to PR #88 and #75.

I am working on an app that makes use of Dizda_cloud_backup to be able to make backups of the DB when needed.

Then the same app also has a bundle written for it that allows the entire app to be upgraded when needed. But upgrades can go wrong at times, so it is written to make a backup first of the DB and the app files itself using dizda. To be able to also backup the app files I have to tell dizda about its location.

This is where the getter comes in as it can be used to access the ProcessorManager and the addFolder settter of the ProcessorManager is then used to add the said folder.

And a command that will be called from a cron job will also be added to the app. This command will make a backup using dizda (of only the DBs) and then email it to a specific user. Here access to the ProcessManager is also needed to be able to call getArchivePath to include it in the email.

@Nyholm Nyholm added this to the 4.0 milestone Nov 10, 2015
@Nyholm
Copy link
Collaborator

Nyholm commented Nov 10, 2015

Thank you for this. We should thing out a good way for changing the configuration like this.

To get data to email the user, check out #90. Do you think you could get what you need with those events?

@chesedo
Copy link
Contributor Author

chesedo commented Nov 10, 2015

Yes, it seems that those will be a great solution for both cases - using the FilesystemEvent to be able to add the extra folder (as is suggested) and possible getting the backup (or just the name) from the BackupEvent.

These events will then probably also make the setters added in #75 obsolete.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants