Closed kbarros closed 8 months ago
Can we store the contributed docs build as a tar-gzip and then download from https://raw.githubusercontent.com/SunnySuite/SunnyContributed/main/contributed-docs/build.tgz
For the download: https://docs.julialang.org/en/v1/stdlib/Downloads/#Downloads.download For extracting: https://github.com/JuliaIO/GZip.jl and https://github.com/JuliaIO/Tar.jl.
Alternatively Zlib supports a multi-file archive out of the box, but seems to be less maintained? https://github.com/fhs/ZipFile.jl/blob/master/src/Zlib.jl
Another option is to store the docs build on a separate branch, say docs-build
. Then it can be cloned efficiently using:
git clone --single-branch --branch docs-build git@github.com:SunnySuite/SunnyContributed.git
If it ever gets too big, we can wipe out the history on docs-build
and recreate.
I think I favor your first suggestion -- just make a tar and download it. No need to periodically wipe histories to keep the system behaving. I'll try it out.
Fixed in #213.
It appears that our docs build is not actually performing a sparse checkout of https://github.com/SunnySuite/SunnyContributed/tree/main/contributed-docs/build. The output below, from running
docs/make.jl
, indicates 21MB are downloaded, even though the files are small. I wonder if the history has some large files that were removed. cc @ddahlbom.