What to do about the cylc central suite database?

[cylc]

The central database was intended as a means of sharing suites between cylc users at a particular site. Currently, however, it is not network aware and is implemented as a very insecure world-writeable common directory space, and is generally only used for making cylc example suites available to users.

I originally intended to put the central db on the network, at the least, but I had never really thought of an effective way to handle suite discovery, meta-data, and revision control. So ...

[cylc]

It has been suggested, and I think I agree, that we should remove the central database entirely and leave suite sharing up to users or sites, because this feature is inevitably closely tied to revision control and meta-data driven suite discovery, which should probably not be cylc's responsibility.

Suite sharing between light cylc users can easily be done by means of communication and mutually readable storage locations (normal Unix home directories, typically).

The current main use of the central database is to make the example suites available to users. This could easily be replaced with a CLI tool to import the example suites directly into private databases.

[cylc]

The central database was removed at cylc-4.5.0.