Config with serde & ssh port

[TheAlgorythm]

The configuration could look like this:

[remote]
host = "some-server"
user = "some-user"
ssh_port = 42
temp_dir = "~/some-dir"

All config options are optional. A check for having a host & user specified, either through cli or config, has to be implemented.
But an alternative could be to allow multiple remotes and picking either the first or one which was specified with a name in the cli (Information for myself: serde-piecewise-default has to be used).
I splitted the host and user into 2 separate entries but I could change that.

The changed command arguments are untested and derived from #13.

[sgeisler]

Thx for the PR! It certainly makes the code base more idiomatic. I take from the WIP status that you are still working on it. I still left two comments.

[TheAlgorythm]

Which configuration possibilities do you prefer?

[sgeisler]

Which configuration possibilities do you prefer?

I'm not sure I understand what you mean exactly. Ideally every option is available as both config file option and cmd line option.

But generally I have no strong feelings because I don't rely on the tool anymore. If you think a feature/option is useful and have a good argument in favor of it I'm happy to work on the PR with you and merging it eventually, but I'm not actively working on cargo-remote myself for now, so I have no roadmap or anything if that was part of the question. Rust has come a long way and I was clearly a beginner when I wrote cargo-remote, so there's probably enough to fix/do better.

[TheAlgorythm]

What was the idea of an enum Opts with only one option. I changed it to a struct, as passing this opts around is easier. Is there any problem?
I hope I don't bother you.

[sgeisler]

What was the idea of an enum Opts with only one option.

Iirc when cargo calls cargo-remote it called it with remote as first argument and I needed to get rid of it/match it somehow. Maybe there is a better workaround, have you tested this version?

I hope I don't bother you.

No, not at all, I'm happy someone finds the project useful enough to work on it 😃

[TheAlgorythm]

How should we handle changes in the README?

[sgeisler]

At least remove wrong examples, but I'd appreciate it if there was some example config.

[TheAlgorythm]

I think it is ready for merging. If you find any shortcomings please let me know.

[TheAlgorythm]

Do you wait to merge until the next release to not confuse other people?

[sgeisler]

Sorry, I forgot about it a bit, will try to test and merge soon (kinda annoying since it's all manual).

[TheAlgorythm]

Don't hurry

[sgeisler]

Merged 🎉 do you want me to cut a release?

[TheAlgorythm]

It could be a release worth unless there are any changes planned. Btw the readme-field could be added to the Cargo.toml.

[sgeisler]

done