Closed bbest closed 11 months ago
I 2nd this approach.
My only concern with google photos is potential data loss in the future if google accounts get lost or deleted. However, I do not know of a better (free) service to suggest for this. I use google photos for my personal photos and would recommend.
It looks to me like the latest failed travis build may have stalled for this reason ( the build took >10min to clone).
@eqmh : Let me know once you get the photos moved into g-photos (or elsewhere) and I will help prune them from the git history tree.
Hey @bbest, @7yl4r,
Removing imagery from the repo and adding the 'here' package fixed Travis CI bugs. Good call!
I am closing the Travis CI issue now. I will also move imagery into g-photos.
Hi @eqmh,
We should figure out a different image storage strategy other than Github, which should be used for versioning code, not 1.2 GB of imagery (and we're just getting started). The individual repository limit is 10 GB. This also adds a lot of bulk to the repository for files which don't need versioning and slows down the website editing process with the time-consuming pull (and push if including in output website).
I recommend we:
Transfer all the images in
survey imagery
into a shared album in Google Photos.Permanently remove this folder from the repository and its history to reduce the repo's size:
Embed gallery like so: How do I embed a Google Photos album into a website? - Public album .org
PS Here's what I saw when first trying to pull repo with
1.22 GiB
to receive: