Hello! In development it's really nice to have changes be re-compiled on file save. This usually happens when I do a normal

cargo run

. However, when I run

cargo shuttle run

for development, it doesn't look like it detects the changes. Is there something I missed in the docs related to this? Is this the way you're supposed to do development with shuttle? When I just do

cargo run

, I get errors related to missing

--port

,

--storage-manager-type

and

--storage-manager-path

. When I put in values for these (for example,

cargo run -- --port 8000 --storage-manager-type working-dir --storage-manager-path .

) then it doesn't look like anything is returned when I go to http://127.0.0.1:8000/hello. I am using the examples github repo (found here: https://github.com/shuttle-hq/examples) and am trying out the

rocket/hello-world

example. Any help would be appreciated!

Does this help? https://discord.com/channels/803236282088161321/953005742842069013/1084033558315806740

After 0.12, you can do

cargo watch -x 'shuttle run'

without ignoring any files.

@alert-air-2447 @gentle-ice-1561 Ah, I see now. I did try that command before, but what was throwing me off was on file save VSCode was doing a ton of cargo checks before re-compiling and was taking a long time, so I assumed I was missing something. I ended up turning off this setting in VSCode and now the hot-reloading works like a charm 🙌 Thanks for the help guys!

nice!