Máté Cserép

In my opinion it is already complicated to use the command-line interface of CodeCompass, often even the developers of the project has to look up the documentation about the various...

The used configurations should also be persisted in the workspace directory anyway, even if given through the CLI. We already store some project information in the workspace directory in JSON...

In conclusion, implementing both approaches would be the best 😄 A typical solution is that CLI arguments override config-file defined arguments.

Can we target the main objectives to achieve the goal this issue? - CSS sources of the plugins shall be decomposed (#22). - Plugins shall only depend on their own...

> I support the idea, but I am afraid tar ball will be the main deployment technique for many of our customers, especially internal ones. The main problem with tar...

> Typical customer who wants to try out CodeCompass has no sudo right. Can we use snap package in that situation? I don't think so. I get your point then.

The selection of the most fitting package manager system is open for discussion, I will make the title of this issue more broader about that. A remark @whisperity: snap is...

Separate common tables (nice oxymoron) would introduce a couple issues hard to tackle I think. Just to mention a few: - plugins working on common tables (like the *search plugin*)...

We should warm up this topic @bruntib following the discussion last week.

> With this patch the page load and every network request take a few seconds. Everything became slow, so this needs some debugging. I'll try to investigate too. Apart from...