Multiple servers

[Steve2Go]

Hi! Love what you've done so far - I've had a quick play and it's pretty stable.

Only thing is, I use 2 servers.

Would you be interested in adding server selection (I understand that there's no server UI yet) or accepting a PR if I have a crack at it? (fair warning, this would be my first crack at swift)

Either way, this app needs more attention from public - it's very nice looking 🙂

[Hamuko]

I'll preface this by saying that I don’t use multiple servers and I doubt that I ever will, so I am not particularly interested in doing any work towards it.

I think my primary concern here is how it’ll be implemented and what kind of a maintenance burden it will be. Currently there aren’t a lot of settings in Dreadnought so the problems wouldn’t be evident right away, but might become more and more apparent in the future.

For example, I’ve played with the idea of adding a directory mapping feature, so you could map /server/downloads to a local directory on macOS, say /Volumes/ServerDownloads/, and then directly open qBittorrent files that are available via a mounted network drive straight from Dreadnought. If this feature was added, would it need to be added for each server individually? What will the user interface for it look like? How will the code side be implemented so that it doesn’t become a massive manual work to figure out what settings are active at a given time?

[Steve2Go]

To be honest, I agree - the lack of complexity is where the stability comes from, which takes restraint.

With that in mind, I think on first thought, I'd implement it as a simple menu like,
Server1
server2
Add a server
Delete A server >
- Server1
- Server2

Adding a server would use the existing UI.

The only config file change necessary would be something like:
<servers> <server> <key>ServerURL</key> <string>...</string> <key>ClientCookie</key> <string>...</string> </server> </servers>

In this way any future additions by you would be at your discretion to add inside or outside of the server block.
By choosing another server, you'd unload the config in its entirety and reload it back in with the current server - essentially "switching servers" as opposed to being "Multi Server"

Thoughts?