systopia / config-profiles Goto Github PK

I recently added stats to the Twingle profiles:

• usage count: how often was this profile used?
• last used: when was the profile used the last time?
• first used: when was the profile used for the first time?

This makes profile life cycle management (i.e. "can I delete this?") a lot easier, as well as for debugging or just general book keeping.

Potentially we would have to exclude these columns from extended logging, so we don't bloat the DB.

There might be a point in adding a "selector" property to the data model, so we can deal with cases where the user of the profile (e.g. an external service) doesn't know about the (internal) profile ID, and would therefore need another criteria to pick the right profile to use. This could, for example, be an (regex) expression, or a simply a list of external keys.