[x] Alter the model for member to add a membershipType that is external. This allows inserting an external member (or members) that provide service nodes from non-members.
[x] (Optionally) Alter the model for health_check to add a row that lets us know whether the check was made on a member's or an external node. This can be called checkOrigin, but I'm open to ideas.
[x] Insert several external (i.e. level0) members for each service published on external.json with membershipType: external and membershipLevelId: 0.
Add a worker that updates the list of members' and non-members' nodes at regular intervals. This might be a cronjob (i.e. Repeatable) process directly attached to BullMQ.
[x] This process might replace the same process on post-migrations since it can be run once the server process begins.
[x] This process would attach the list of non-members' service nodes to the external (i.e. level0) member.
[x] This process would review the member_service table to update each member's services.
[x] (Optional) Modify f-check-service.js to fulfil the node_origin if it applies.
[x] Modify the UI to either add a filter or a separate view to see the checks on external service nodes.
memberto add amembershipTypethat isexternal. This allows inserting anexternalmember (or members) that provide service nodes from non-members.health_checkto add a row that lets us know whether the check was made on a member's or an external node. This can be calledcheckOrigin, but I'm open to ideas.level0) members for each service published onexternal.jsonwithmembershipType: externalandmembershipLevelId: 0.serverprocess begins.level0) member.member_servicetable to update each member's services.f-check-service.jsto fulfil thenode_originif it applies.