Lann

Ok not too surprising; thanks for trying. I can try something else but we might need to drop php.

Turns out we were holding it wrong; you have to include the php file in the URL, e.g. `http://localhost:3000/index.php`. Not a good UX both in terms of not supporting an...

This issue is linked by a Spin error message if we detect these modules but I think we can close and I'll just add a note to the top.

I would suggest another check: `git -C rev-parse` If this succeeds then `` is already (within) a git repo and `git init` should be skipped. This will avoid creating unwanted...

It turns out this is only an issue for Grain with debug builds. [Compiling with `--release` solves the problem.](https://github.com/grain-lang/grain/issues/2152#issuecomment-2315678001)

No my understanding is that this is working as intended on the wasmtime side.

> Where shall we publish the initial set of environments? `fermyon.com`? > Where shall we maintain the environment WITs? I'd suggest "next to the code that implements them"; ideally _generated...

A slight variation to consider here would be to only rename (re-package?) those interfaces that are actually getting breaking changes. While this would make things less consistent, it would also...

As anticipated, `"@example.toml"` does in fact give me feelings :slightly_smiling_face:. While `@file` is a pretty common convention in CLI args, I _personally_ prefer more explicitness where more structured typing is...

This seems sufficiently design-laden to be worth a SIP.