(1.) main Program ... uses a test that before and after backup folder structure matches; a method actually makes the backup #34
Description
to the output of the rakefile, to be saved.
ruby file to respond... if rakefile output does not have failures.
tasks in Rakefile.rb
(already incorporated)
task 1: Backup_Original - note: if files were lost by the program. (already incorporated)
(not incorporated)
task 2: either overide most_recent_backup or dont overide most_recent_backup
task 2: -note: before we override we rspec to see file structure correct.
(not incorporated)
task 3: if submodules broken on github... faulty submodule was made.. rspec needs to figure out.
task 3: -note: dont know how yet but we need to figure it out.
note note: if something went wrong with rspec checking ...
then, test main. tell fail. prompt user "oh noo! We did not update your most recent backups because we think something went wrong." "Take a look on github to make sure nothing is out of sorts. If something seems out of sorts; run either command... restore to previous most_recent; or ..."
((warning) before you do this second one. you might lose stuff if you do not pay attention because it goes back to original: "Also, you could restore to original backup but that is not recommended
call us if you really run into issues and we will talk you through this tough time.")