ini file: clarify that beaker.session.key should be unique When several instances of Kallithea are running on the same machine, the same browser cannot be logged into both instances at the same time without conflicts. The login session are saved into the same cookie; logging into one instance closes the session on the second instance and vice-versa. This is caused because the cookie name is simply 'kallithea', combined with the fact that the cookie specification (RFC6265) states that there is no isolation of cookies based on port. This means that the browser sends all cookies from a given domain with all services (Kallithea instances) running on that domain, irrespective of port. The services thus need to handle any such issue themselves, for example by using unique cookie names and only interacting with one's own cookie. Making the key unique when creating the configuration file proved difficult: - it does not seem possible to hook into 'paster make-config' - since Beaker directly interprets the beaker.session.key, changing it on the fly from SessionMiddleware will not work correctly. There is a kallithea-config script that is an alternative to 'paster make-config' which would be the ideal place to make such changes. However, it seems this method is not advocated over 'paster make-config' (yet?). Instead, simply add a comment in the config file and let the user take care of it.

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.