`wasp new -t saas MyCoolSaasProject` is slow

[Martinsos]

For some reason it is quite slow till it check out open saas repo, takes like 10 seconds or something. I am guessing the git command that pulls in the data is probably pulling in too much? Maybe we don't pull in just the latest commit, depth 0 or what is it, but more? Look into it.
Confirmed on wasp version 0.16.x, and also the latest one.
I haven't tried any other versions, or other starter templates (which we should also check while at it).

[infomiho]

Tested it now and it's really slow:

wasp new miho-saas -t saas  2.82s user 1.37s system 21% cpu 19.140 total

[cprecioso]

On further review:

• The download does not do any git operations, it downloads the .tar.gz of a tag. (GitHub automatically creates that for each tag)
• These archives are heavily throttled on GitHub's side to conserve resources:
  • The archive has almost zero compression applied
  • The download speed is very limited
• The problem is that the archive (as of 0.18) has two main folders:
  • opensaas-sh (81.2 MB): the opensaas website (with e.g. heavy assets)
  • template (13.6MB): the actual template
• wasp new only needs the template folder but it downloads the whole thing, 6x more data than needed, and at very low speeds.

We should find a way of downloading only the template folder, and preferably in some other way than the auto-generated archives.

[Martinsos]

Uff ok! I guess we can just run git command and use it to download only content of template dir, from specific tag, depth of 0 or 1 or whateveris correct depth?

[cprecioso]

I guess we can just run git command and use it to download only content of template dir

Yeah we might, but we don't require git installed for our users, that'd add a new requirement. I think I can find a workaround.

[infomiho]

User reported this as well: https://discord.com/channels/686873244791210014/1420096261423501353/1420096261423501353

[cprecioso]

Based on a quick Discord poll, I'm working on the following solution design:

On pushing or editing the release tag for opensaas, a github action automatically runs. It archives only the correct folder ahead of time and adds it to the release. This will get then get served through GitHub's CDN, much faster.
This is not a complex release pipeline, just a script with on: tags that contains basically git clone && tar -c && gh release upload.

Then we modify the compiler so it fetches this archive instead of the dynamically-created github tarball.

Working at wasp-lang/open-saas#511