config.xml utility ?

[promeneur]

Today, the tumbleweed rpm fah-client-bastet-beta was updated.

The config.xml was replaced by an empty one (no custom data). There are only comments about an example.

It seems fah-client ignores config.xml and takes care of my folding account data. Am I right ?

In this case, what is the utility of config.xml ?

[Joe_H]

As I understand it, at installation and startup time the v8 client reads config.xml and uses that for some settings. The config.xml file is not updated with any changes made within the v8 client through the web interface. Not all v7 settings in config.xml are compatible with v8. At this time there are some expert settings that can only be set in the v8 client by entering them into config.xml and restarting the client process. Those may be added to the web interface in some future version.

[calxalot]

If you are upgrading from v7 some settings are imported on first run. The default config.xml is otherwise basically empty.

The rpm package you are talking about probably does not import/copy the v7 config.

[calxalot]

And yes, there are v8 settings that can only be set via config.xml.

Or via command line arguments.

[promeneur]

If you are upgrading from v7 some settings are imported on first run. The default config.xml is otherwise basically empty.

The rpm package you are talking about probably does not import/copy the v7 config.

I did not switch from v7 to v8.

This is an update of an already installed fah-client-bastet-beta.

The update only saves the previous config.xml to config.xml.rpmsave

[calxalot]

No worries then. v8 stores config changes in client.db in the client working directory.