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
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.
- Integrated EventEmitter2 for async event processing
- Changed jshint reporter module URL to avoid use of SSH
- Core can disconnect a service node, generates many events
- Service Node can disconnect a Core, generates many events
Nothing yet processes those events. Many things need to be cleaned up
and removed based on a Core Node disconnection. The Core itself needs to
remove all Kaleidoscope events and other data received from the Service
Node, and the Service Node needs to remove all CoreUser records (and
everything they did while there).
That's going to take a minute to implement throughout all the systems.
- Moved the responsibility of expiring Announcements from MongoDB into
the Reeeper
- Added logic to clean up comments attached to an expiring Announcement
- ResourceStats are now much more universal and common
- CommentStats are for comments only
- More routines to comment on and vote on "content resources"
Andrew Woodlee