feat: dynamic config

[reneca]

New release with dynamic config reloading.
It'll be useful to not implement any type of remote command.
It replace what it was sketch before and imply a release.

[oschijns]

When creating a ProSA from scratch, the Cargo.toml still uses previous version.

$ cargo prosa --version
cargo-prosa 0.5.0

[package]
name = "my-prosa2"
version = "0.1.0"
edition = "2024"

[dependencies]
clap = "4.6.1"
config = { version = "0.15.25", features = ["toml", "yaml", "json", "convert-case"] }
log = "0.4.33"
prosa = "0.4.3"
prosa-utils = "0.4.3"
serde = "1.0.228"
tokio = { version = "1.52.3", features = ["macros", "rt", "rt-multi-thread"] }

[build-dependencies]
cargo-prosa = "0.4.2"
toml = "1.1.3"

[oschijns]

Some additional tests I tried:

• Modifying the config file with a text editor triggers a configuration reload. ✅
• Copying another config file over the one used by the ProSA triggers a reload. ✅
• Deleting the config file and creating a new one does not trigger a reload. ❌
• Moving the config file and moving it back triggers a reload. ✅
• If the ProSA's config is a symlink, editing the destination of the symlink triggers a reload. ✅
• If the destination of the symlink is deleted and recreated, there is no reload. ❌

[reneca]

Yes cargo-prosa use the latest release when it import modules.
From your test (we discussed about it) the config file should not be deleted. It's a non sense, ProSA can't run without a config file. So if the config file is deleted ProSA will keep the same config until its shutdown.