itowlson

Are you suggesting we set up git config, or set a remote? I'd be extremely wary of that. Running `git init` for them is about as far as I'd want...

I am okay with that. So the proposed behaviour is: * By default, `spin new` attempts to run `git init` in the newly created directory. * `spin add` does NOT...

Checking environments adds an appreciable bump to the time to run `spin build`. I looked into caching the environments but a robust way didn't really help - the bulk of...

This is now sort of a thing and can possibly be looked at. Outstanding questions: * Where shall we publish the initial set of environments? * The wkg configuration will...

Okay I have pencilled in `fermyon.com` as the default registry for environment definitions (with !NEW! the option to override it or use a local path !NEW!). One thing that occurred...

Implemented caching on the basis of immutability as per Till's comment https://github.com/fermyon/spin/pull/2806#issuecomment-2364170164 (and double checked on Windows). I'll have a think about the lockfile idea. A lockfile mapping environment IDs...

I did some unscientific performance testing with this. Validation for local or HTTP components is quick once registry targets are cached. If they have local dependencies, then composition before validation...

@tschneidereit > Aren't environments also just packages though? Ones that we apply some additional semantics to, yes, but not ones that are someone non-standard. Yes and no. I found that...

The environment package I am using for testing: https://github.com/itowlson/env-wits The `deps` directory is identical to the Spin `main` deps directory, but as noted above I had to make some tweaks...

Okay another nasty with the "environments are just packages" thought process is that environments do a bit more than "world" packages, in that they have to map triggers to worlds....