jonaro00
jonaro00
You'll need to update templates.toml to point to the correct manifest directory to fix CI.
sqlx 0.8 is supported since v0.48.0
It might not be possible with the closure that you return when using ShuttleActixWeb, but if you expand to implement shuttle_runtime::Service yourself, this code should fit into that. https://docs.shuttle.dev/templates/tutorials/custom-service https://github.com/shuttle-hq/shuttle/blob/main/services%2Fshuttle-actix-web%2Fsrc%2Flib.rs
Can you also test the interactivity of the subprocess, i.e. that the y/n prompts work as intended when you don't have cargo-binstall?
I suppose it would do something like this for you? https://www.sea-ql.org/SeaORM/docs/install-and-config/connection/#connect-options Worth considering.
The version of salvo your crate uses has to match the version that shuttle-salvo depends on, which is currently 0.75.0, so if you downgrade it should work.
Updates to shuttle-salvo coming soon
On the new shuttle.dev platform, there will soon be a re-deploy feature that creates a new deployment as a "copy" of an older one, which is effectively a rollback.
We patched this issue by reducing the default timespan from 7d to 24h, and we will keep looking for ways to improve fetching and browsing logs.
Try declaring them as build assets https://docs.shuttle.dev/docs/files#build-assets