As it is not allowed to post screenshots (or other pictures) in the development forum, that thread will be continued here.
Some screenshots of what I've build so far (scripts come later as I just discovered a -cosmetic- bug).
The scripts will backup 'projects' in some folder (in my case c:\develop) to a backup location (I tested with c:\backup\develop).
Every time you backup those projects, it will only copy new or changed files to this backup location.
That is done in a folder structure similar to c:\backup\develop\project1\<timestamp>\path\to\your files.
That way you can always go "back in time" to the *exact* state it was in at the moment of <timestamp>, without copying a file multiple times to the backup location (if it hadn't changed).
Whenever you made some changes to your project that are worth saving for later, you start the (PowerShell) script that will take of it all.
After starting, it will ask for each changed project to describe it. That is convenient if you want to restore files (more on that later)
A few screenshots will probably make it more clear.
Start the PowerShell script to start the backup process. That will show you this dialog:
After selecting a category of your changes, you are asked to describe the changes:
That's all. If there are more projects that changed since last time you ran the script, you will be asked the same questions for that project. The titlebar of the dialog boxes tell you which project you are describing.
In the end, this is what you will see:
That's all for backup.
Restore: Start another PowerShell script:
After that, you will see a window you might recognize: Everything!
In Everything, select the files you want to restore and press <Enter>
Now select the folder where you want these files to 'land'. The c:\develop\projectname folder is pre-selected, but you can restore your files to any other location too. Be careful: existing files will be overwritten without further asking.
And that's it. The selected files are restored. Last screenshot to show that the files are actually restored:
As said, scripts will follow later ..
Version Control, part 2
Re: Version Control, part 2
Forgot to post the scripts ...
Don't think anyone will ever take a look at it (let alone use it), but it's good to have an off-site backup
Recipe:
- extract zip to empty folder
- Add Everything.exe (needed for monitoring filesystem changes ànd for selecting files to restore)
- Change the settings in both Snap-In.ps1 and Snap-Out.ps1
Now you can interactively backup and restore 'projects' with those 2 scripts.
Run Snap-In.ps1 unattended (for scheduled tasks etc) with command:
Powershell.exe -File "C:\Path\To\Your\Snap-In.ps1" -AutoSave
EDIT: Updated to version 2.2 (was 2.1)
Don't think anyone will ever take a look at it (let alone use it), but it's good to have an off-site backup
Recipe:
- extract zip to empty folder
- Add Everything.exe (needed for monitoring filesystem changes ànd for selecting files to restore)
- Change the settings in both Snap-In.ps1 and Snap-Out.ps1
Now you can interactively backup and restore 'projects' with those 2 scripts.
Run Snap-In.ps1 unattended (for scheduled tasks etc) with command:
Powershell.exe -File "C:\Path\To\Your\Snap-In.ps1" -AutoSave
EDIT: Updated to version 2.2 (was 2.1)
- Attachments
-
- Snap-In-Out v2.2.zip
- (11.34 KiB) Downloaded 231 times