Create missing config directories and files on startup

[esavier]

Simple feature, but i don't know how to bite it from rust standpoint.

Technically, it would be awesome to create the default config file if it's missing. This also entails creating default directories. It may be done on setup, but since horust is working on top of cargo, cargo install just copies exec to bin location.

Right now, without it, Horust just bails out with ENOENT.

can be done either on startup or installation

• dump default config to file if it not exists (/etc/horust/horust.toml)
• create directory tree (/etc/horust/xxx )

[FedericoPonzi]

Can you please provide the environment and command run in order to reproduce it?

If you're referring to service config files, how would you generate them? Horust would need a way to know which service the user wants to run. Also, I think using the --generate-sample > sample.toml might be of help here, and for single runs you can just use wrap the command with horust, like horust -- my-command.

I hope I've answered your question, if not please clarify. I'm very interested in improving ux!

For the cargo dependency part, it's just because it's still in beta. I also think the version available via cargo is not in sync with master, so I would suggest to directly compile from the repo if possible. I have plan to create a release on github page as soon as feature set is stablized.

[esavier]

services are not as much of a problem, since producing those from thin air is impossible imo,
biggest problem is lack of directory tree on startup ( /etc/horust/... )

it is quite confusing after horust installation that it reports EOENT, and Error: HorustError { kind: Io(Os { code: 2, kind: NotFound, message: "No such file or directory" }) } which says nothing. I understand it is in the documentation, but it shouldn't be a manual step.

also it should dump default config to file if it not exists ( /etc/horust/horust.toml )

i will update the Issue with checklist.

[FedericoPonzi]

That error message is definitely not user friendly. I think I've recently updated that section of the code to be more informative. In any case, I would like to have a MRE, because I think horust should work by using some defaults instead of relying on the config defined in /etc/horust/horust.toml. I'm also thinking that if horust is not run as root, it might not have access to /etc. OFC, we could add a new parameter for dumping the config file, like the sample service config option. In that case, the user is also free to create the config file in whatever path she prefers. WDYT?

[esavier]

I would like to start working on this if you dont mind :)
I think we can meet in the middle, and do two features at once. I think it is possible to both provide default config on demand, and to be able to adapt to missing or incomplete one by defaulting the values.
I will do some research, prepare PoC and we can discuss it then

[frondeus]

Hi, I really like Horust, and I see there was no progress regarding this issue.

About improving error messages, would you accept a PR that introduces anyhow and the Context trait?

That would solve human-readable errors. I could prepare a PR that would add useful context messages like in which .toml there is an error, or which directory is missing.

Unless you would like to "crate-ify" this tool. In that case anyhow is not the best solution.

[FedericoPonzi]

Hey Wojciech,
Unfortunately I've been busy with other stuff lately and couldn't spend time on Horust. There are no plans to crate-ify it, if you're up for it I'm more then happy to assign this to you! Anyhow would be more then perfect. Thanks!

[frondeus]

No problem :)
The best part of open source is that I can always fork it, check it and then if you like it - merge :)

[FedericoPonzi]

Thanks a ton! I've just assigned it to you, feel free to open a draft PR if you want early 👀 and comments!