You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Presently the web-map only supports one Factorio server, as the URL is hard coded. However in the Kafka topics most (all?) messages are keyed by a Server ID - so that's a good start.
Supporting multiple servers requires authentication. It's possible to send a token along with a syslog message. This could be a JWT that contains a server ID. All messages must contain a server ID, and that can be mapped to a name. The tile-server can then use a new directory for each Factorio server.
events-server: Add some sort of authentication that will check incoming messages for a JWT token, and verify it
web-map: add a new path per server? Not sure how to do this
events-server: websocket clients should send a server ID and only subscribe to events for that server
events-server: a table of registered servers, along with pertinent data (contact info, server name)
Out-of-scope
Nice to haves, but not necessary. Maybe in a later ticket.
web-map: an overview page of all servers
Kafkatorio portal: a web page where server owners can register a server and create their own keys
The text was updated successfully, but these errors were encountered:
aSemy
changed the title
Allow for multiple Factorio servers
web-map: Enable support for hosting multiple Factorio servers
Jul 17, 2022
Presently the web-map only supports one Factorio server, as the URL is hard coded. However in the Kafka topics most (all?) messages are keyed by a Server ID - so that's a good start.
Supporting multiple servers requires authentication. It's possible to send a token along with a syslog message. This could be a JWT that contains a server ID. All messages must contain a server ID, and that can be mapped to a name. The tile-server can then use a new directory for each Factorio server.
Out-of-scope
Nice to haves, but not necessary. Maybe in a later ticket.
The text was updated successfully, but these errors were encountered: