I use git-http-backend, which doesn't seem to support archive: https://git-scm.com/docs/git-http-backend
Why not use a shallow clone (as a fallback)?
```
git clone --depth=1 https://git.sprovoost.nl/instablossom.git
```
README not rendering
I'm not seeing my README.md on the landing page: https://gitworkshop.dev/r/naddr1qqxxjmnnw3skymr0wdek7mgpp4mhxue69uhkummn9ekx7mqzyzrgt6l0vefn3htfx83veheur8vlpedpqe7frrezuuypcf2clra0sqcyqqq80xg9sng4n
Discussion
I considered that and experimented with it. There is a lack of support to do it in the browser. In any case, it is too heavy to do client side. And too slow / bandwidth inefficient to do on demand on the server-side. It could potentially be done as a job run daily but it is ultimately reliatively expensive operation to run give we are just looking for the readme.
Why not have "git push" post an update Readme as nostr longform note or something like that? (if modified)
The nostr:nprofile1qqsggm4l0xs23qfjwnkfwf6fqcs66s3lz637gaxhl4nwd2vtle8rnfqprdmhxue69uhhg6r9vehhyetnwshxummnw3erztnrdakj7qfqwaehxw309ahx7um5wghx26tww4hxg7nhv9h856t89eehqctrv5hsz8rhwden5te0w35x2cmfw3skgetv9ehx7um5wgcjucm0d5hsjmvd7t team suggested displaying a repository nostr wiki page instead of the readme in the git repo.
We could definity do that or the `git push` thing but don't we ideally want to support display other files and potentially at other refs?
If we end up in a world where users of #GitViaNostr don't just rely on free (beer) and reliable hosting from big players like github, bitbucket, gitlab, etc. But instead use selfhost or #GitViaNostr hosted solutions like 'song' could be then the git servers could serve all files for all refs. That would provide the best UX.
We actually store our wiki pages as Asciidoc in the GitCitadel repo, so simply displaying the Asciidoc files gives us a similar result.
If GitWorkshop can deal with Nostr-style wiki links and other Nostr addresses, then it'd be added value.