Zanata-style: ~/.config/csprocessor.ini fragment: [servers] production.url=http://someurl production.apikey=someapikey test.url=http://testurl test.apikey=someapikey Then, when a csprocessor.cfg is used, it will have a URL attribute in it: SPECID=5322 SPECNAME=Name_of_Book URL=http://someurl So the csprocessor can then match the csprocessor.cfg URL with a csprocessor.ini .url property, and use the .apikey to communicate with the server. This means that "projects know which server they are stored on".
actually, the csprocessor.cfg key should be something like SERVER to make its purpose more evident to the user.
When a csprocessor command is run with the -s switch, no apikey is required at the command line if it is present in the csprocessor.ini
Added in 0.22.0. The client now has the ability to have multiple servers. A "default" server must always be specified so that it has something to go back on. The csprocessor.cfg uses the "SERVER_URL" attribute as it is more meaningful then plain "SERVER" as well. For the username (previously apikey) it will attempt to match the -H (previously -S) url to a server. If no server matches then it will default to the "default" server. The whole csprocessor.ini format has somewhat changed as well. See Bug #796009 for more details.
Closing and setting as current release as no QA was performed by the original reporter. If there is still an issue with this bug still than please re-open it.