You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As we start movingg towards running more Domino actions through Vagrant instances (for example, #1240), we would like to have a good system to revert changes,
@JustinProminic proposed that we do this by backing up the design documents from the target databases. These backups could be saved in a central database or in a database for each server/database. @dpastov is exploring the basic design for this.
I expect most of the logic for this to be on the Domino Vagrant side, but in Moonshine we would want an interface to view and restore the backups. I writeup more details on this after we have a working proof-of-concept on the backend.
The text was updated successfully, but these errors were encountered:
As we start movingg towards running more Domino actions through Vagrant instances (for example, #1240), we would like to have a good system to revert changes,
@JustinProminic proposed that we do this by backing up the design documents from the target databases. These backups could be saved in a central database or in a database for each server/database. @dpastov is exploring the basic design for this.
I expect most of the logic for this to be on the Domino Vagrant side, but in Moonshine we would want an interface to view and restore the backups. I writeup more details on this after we have a working proof-of-concept on the backend.
The text was updated successfully, but these errors were encountered: