Hello All,
If you would kindly take a look at the proposal and comment, I’d very much appreciate it.
Thank You,
-Tony
I commented directly on GitHub.
How do you measure the interval between exports per project?
So what I currently have set up for myself is that, every 60 minutes, a zip backup of all projects at once, and the keystore, if one exists, is made. The code is set up to measure the interval in minutes like this:
private class EnableAutoBackupAction implements Command {
@Override
public void execute() {
Ode.getInstance().setUserAutoBackup(true);
createSettingsMenu();
createAutoBackupTimerTask();
autoBackupTimer.scheduleRepeating(1000 * SettingsConstants.PROJECT_AUTO_BACKUP_INTERVAL_MINS * 60);
MessagesOutput.getMessagesOutput().addMessages("AUTO BACKUP ON - every " +
SettingsConstants.PROJECT_AUTO_BACKUP_INTERVAL_MINS + " minutes");
}
}
The constant, as defined in SettingsConstants.java, is:
public static final int PROJECT_AUTO_BACKUP_INTERVAL_MINS = 60;
If a user does a manual backup in between the set interval, that does not affect when the next auto backup is made. The interval is always measured from the time the last auto backup was made.
I have a couple of hundred projects, built up over years.
I might edit maybe two of those a day.
I don't think my PC or MIT's servers could survive the hourly
tidal wave of backups such a setting would produce.
Is there an incremental backup alternative, where the last backup timestamp
is kept with the user profile, and only projects with a modified timestamp after
the user's last backup are downloaded?
1 Like
LOL 
Wow, I didn’t consider that scenario.
Yes, given the possibility of what you describe, that refinement definitely seems to be justified. I will look into it.
Thanks,
-Tony