Build succeeds but application does not run. about spin

[itowlson]

Oops sorry missed part of the question. The recommended application structure would be similar to HTTP - subdirectories under spin.toml, and component per subdirectory using workdir to hook them up to spin build.

[tpmccallum]

Part 2 on this topic ...

Is it possible to have a single application listen to more than one Redis channel? The reason for the curiosity is that spin add does not facilitate tacking on additional Redis components in the same application:

$ spin add redis-rust
Template redis-rust doesn't support the 'add component' operation

If someone did want more than one Redis component, and this is possible in Spin, what would the preferred application structure be?

[itowlson]

The user has added the component with the wrong path.

We can't error on the build because the build has succeeded - both build steps have correctly created the same output, at target/wasm32-wasi/release/redis_rust.wasm. It's the path in component 2 that doesn't match the build.

[itowlson]

It would be easy to add spin add support to the Redis template - just nobody invested the time to do it.

(If you're interested, I can show you how - otherwise please raise a separate issue and I can do it.)

[tpmccallum]

I would be interested in adding spin add support to the Redis template. Yes please.

[tpmccallum]

Great! I love that subdirectory and workdir config; it's neat!

[tpmccallum]

I will close this and contact you for a spin add tutorial :)