Transition away from current server discovery #18

New Issue

2026-09-14T06:45:18-04:00

josh commented

2026-09-14 06:45:18 -04:00

Now that EC owns the full server lifecycle, we should no longer rely on the discovery method of the folder itself as a means of listing all of our servers. We should store this information in our db server side. This will likely allow us to clean up our interpretation of the different server states

Ex: Server reads as RCON Timeout for the first 1-2 poll attempts after a restart, but this should be expected behavior. EC should know that it's not a true RCON Timeout because it should be watching the Komodo Deployment which at that point would show "health: starting"

Until the Komodo Container claims to be healthy started, there is really no point to relaying any information to the user, or even conducting those initial RCON polls in the first place

Now that EC owns the full server lifecycle, we should no longer rely on the discovery method of the folder itself as a means of listing all of our servers. We should store this information in our db server side. This will likely allow us to clean up our interpretation of the different server states Ex: Server reads as RCON Timeout for the first 1-2 poll attempts after a restart, but this should be expected behavior. EC should know that it's not a true RCON Timeout because it should be watching the Komodo Deployment which at that point would show "health: starting" Until the Komodo Container claims to be healthy started, there is really no point to relaying any information to the user, or even conducting those initial RCON polls in the first place

josh closed this issue

2026-09-17 17:30:31 -04:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: josh/electric-cherry#18