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
I'm planning on trying out Solid Start for an internal dashboard-type application that shows realtime statuses and stats.
I want the server side to constantly fetch up-to-date information from a Kubernetes cluster and store it in a Redis database.
Basically, as soon as the Solid Start server starts up, I want to connect to a Kubernetes controller and subscribe to events, updating the Redis database as new information streams in.
I could launch a separate process to do this, but I'd prefer to do this in the same process as Solid Start to simplify deployment, if possible.
Is this a terribly bad idea? If not, what would be the preferred way to do this? Could I just add a setInterval to entry-server.tsx?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm planning on trying out Solid Start for an internal dashboard-type application that shows realtime statuses and stats.
I want the server side to constantly fetch up-to-date information from a Kubernetes cluster and store it in a Redis database.
Basically, as soon as the Solid Start server starts up, I want to connect to a Kubernetes controller and subscribe to events, updating the Redis database as new information streams in.
I could launch a separate process to do this, but I'd prefer to do this in the same process as Solid Start to simplify deployment, if possible.
Is this a terribly bad idea? If not, what would be the preferred way to do this? Could I just add a setInterval to
entry-server.tsx
?Beta Was this translation helpful? Give feedback.
All reactions