Configuration is stored upon each page visit

[christianlupus]

Currently, the config is loaded from the server upon loading any page (this is intended). Unfortunately, the code as provided in the setup routine detects a change in the internal structures and stores the same configuration to the backend again. That means that there are redundant calls and in the worst case, the configuration is messed up (with concurrent requests).

I think that there are multiple ways to enhance this structure:

1. The data should be provided by an initial state (provided by the server core) for the sake of reduced work. This avoids the additional request here to load any configuration.
2. The setup here is the wrong routine as it is intended to construct the Vue object. Instead, the data handling (fetching the config initially) should be done outside the component and the component should use the mounted method instead.
3. Accessing the global state might be better done with computed properties.
4. The update of configuration entries on the server might be more intelligent to only send a request if really needed.

@seyfeb the code basically comes from you. Am I misunderstanding anything here (especially point 2)?