Preserving functionality by offerring a toggle to backup essential links to user's Drive

[sadnow]

This toggle would allow for automatic backup and retrieval of AnKit and its dependencies to a user-specified location.

360Diffusion did this on a small scale, but not fill root directory backups.

https://github.com/sadnow/S2ML-Art-Generator/blob/main/S2ML_Art_Generator.ipynb did this, but I believe it actually made it where the program operated using files from the Drive root directory.

Due to filespeed bottlenecks, it may be more efficient to copy Drive backup files to a Colab session on each run. Either that or copy it to ram. Due to individual file transfer speed bottlenecks, it might be wisest to have this function save a zip file of the root directory rather than doing individual file copies.

• [x] Fork RIFE (a16434f41a8998b6efd9f64b813269ffd8aa5a81)
• [x] Fork Real-ESRGAN (a16434f41a8998b6efd9f64b813269ffd8aa5a81)
• [ ] Backup available Real-ESRGAN models ( personal archive in case redistributing is a no-no)
• [ ] Backup available Practical-RIFE models ( personal archive in case redistributing is a no-no)
• [ ] Implement toggle for automatic backup and retrieval of AnKit and its dependencies to and from a user-specified GDrive location.

---

Complications:

Backing up /content/ using usual methods means that all of Google drive will also be backed up

Potential solution: Download dependencies, create a zip archive of /content/, then mount Drive

[sadnow]

a16434f41a8998b6efd9f64b813269ffd8aa5a81 partially implements this by using forked repos in case a significant change in either Practical-RIFE or Real-ESRGAN bricks breaks AnKit

[sadnow]

• [x] Var named _preserve_in_gdrive