Finally standardizing on the DTP Component definition:
{
logId: 'my-service',
index: 'myService',
className: 'MyService',
}
And I'm not too far from using UUIDs in there, too, so I have one (1)
standard way of referencing them.
- convert LoganService to use the API module
- add logan worker to transmit Logan events from job queue
- added logan worker config to supervisord directory
- updated the other configs
Moved the definition of updateTimestamps from Chat into the library base
App along with the call to update on-page timestamps during the creation
of the App as a convenience.
Any element following the `data-dtp-timestamp` and
`data-dtp-timestamp-format` conventions will have its `textContent` set
to a client-local representation of that date/time.
UserService.create was adapted a while back to accomodate imports, and
was honoring a field named `isAdmin` and/or `isModerator` during create
to set the value of `flags.isAdmin` and `flags.isModerator`.
This change breaks that importer but stops people from being able to
"sign up" with Admin privileges.
Allow the specification of the KaleidoscopeEvent creation date/time.
This allows Sites and Venue to emit their recent history to a Core when
connecting to populate the Core with their content upon arrival.
rob
CyberShell