geopython / geopython-workshop

The Doing Geospatial in Python Workshop (mainly provided at FOSS4G events)
https://geopython.github.io/geopython-workshop
Other
56 stars 22 forks source link

Repo size #105

Open Robinlovelace opened 2 years ago

Robinlovelace commented 2 years ago

Just cloned the repo and see that it's over 1/4 GB. Please consider pruning the repo size to reduce download times and save bandwidth:

gh repo clone geopython/geopython-workshop
Cloning into 'geopython-workshop'...
remote: Enumerating objects: 1770, done.
remote: Counting objects: 100% (87/87), done.
remote: Compressing objects: 100% (33/33), done.
remote: Total 1770 (delta 62), reused 64 (delta 54), pack-reused 1683
Receiving objects: 100% (1770/1770), 39.09 MiB | 1.61 MiB/s, done.
Resolving deltas: 100% (1074/1074), done.
Updating upstream
remote: Enumerating objects: 976, done.
remote: Counting objects: 100% (5/5), done.
remote: Total 976 (delta 5), reused 5 (delta 5), pack-reused 971
Receiving objects: 100% (976/976), 255.45 MiB | 1.94 MiB/s, done.
Resolving deltas: 100% (517/517), completed with 4 local objects.
From https://github.com/GISMentors/geopython-english
 * [new branch]      master     -> upstream/master
justb4 commented 1 year ago

@Robinlovelace true, part is due that we forked from an existing workshop and almost rewrote it. And there may have been some large data files pushed then deleted by accident. So all that history is carried. In the documentation we recommend to download the master zip file, which should be smaller, around 6.6MB:

https://geopython.github.io/geopython-workshop/#installation

curl -O https://codeload.github.com/geopython/geopython-workshop/zip/master
unzip master

On my system the workshop tree with .git history is around 90MB so maybe some pruning has been done. Think you also can clone just the master branch, to save.

Robinlovelace commented 1 year ago

No problem and thanks for the suggestions @justb4. I still think it's worth considering reducing the repo size as it will encourage contributions from the community if the codebase is easy to clone and work with.

Great work in any case, looking forward to trying updated versions of this course.