search

Unvanquished / updater

QML based updater to install, update and launch the Unvanquished game.
https://unvanquished.net/download
15 stars 7 forks source link

idea: command line switch for headless update #14

Open illwieckz opened 7 years ago

illwieckz commented 7 years ago

For server owners, would be cool to be able to do:

./updater --no-gui --install-path=/some/where

I don't know yet if --no-gui would just check for update and download things or must it run the game at the end too. In the later case, perhaps add a --no-run option, to let server owners having one install for multiple servers being sure they keep full control of what they do.

The --install-path would be optional. Once the config file is written, the install path would be reused like in gui mode. Wa can also add a --no-conf switch to not write the config file, it would be useful for benchmarking software, allowing them to install unvanquished for benchmarking purpose without having to mess with user data path (Let's make phoronix benchmarking us again).

Edit: the --install-path would be optionally usable by game managers like lutris or things like that, so it would be cool to have it doing things on gui mode too.

DolceTriade commented 6 years ago

I feel like this is overkill for such a task. We have ./download_pk3_torrent.sh and such that accomplish the same thing. If we want to do headless, we should ship a static aria2c binary with a batch/shell script instead.

illwieckz commented 4 years ago

Static aria2c binary is not a bad idea but it's yet another project to maintain, debug, etc.

illwieckz commented 4 years ago

For testing and debugging purpose I would like to have those options even in graphical mode: --no-config-write, --auto-download, --start-after-download (see #48), --download-only, that's while a --no-gui option or a stripped-down build, console only variant may be a good idea.

DolceTriade commented 4 years ago

We also probably don't want to require QT for such a build, hence the bash script

ghost commented 2 years ago

I would not use a qt application on my server to update when it's simple enough to do it manually.

necessarily-equal commented 2 years ago

I don't think this use case for the updater is worthy of our time — when we add another server, we want to to be unique, and that means it must have its own VM files, and then it basically needs a custom install anyway.

ghost commented 2 years ago

Well, there's a subtle nuance to put to @necessarily-equal though: we prefer servers to have unique settings and/or content for their geographic area. So far, (almost) all servers only notably host SK5 bots which is bot good and bad. but, that's a different topic I believe. Maybe a tool to generate config with presets could be nice though, since unv is fairly poorly documented. I still think, documenting and have complete config example file would be a better spend of time.