jettdc / switchboard-poc Goto Github PK

We need to go in and test to make sure that different variations of the same routes register on different endpoints and subscribe to different topics

Maybe we should allow users to create plugins that allow for the generation of messages on the first connection?

So, say we are making a pizza application, and a user doesn't connect until after their pizza is already on the way. There could be a plugin specified to check the db to look for what the current stage is, and rebuild those missed messages.

// plugin onFirstConnect /orders/3

func plugin() []Messages {
  msgs = []
  if db.GetOrderStatus(3) >= "en-route" {
    msgs.append({
      msg: "Your order has been received"
    })

    msgs.append({
      msg: "Your order is in the oven"
    })

    msgs.append({
      msg: "Your order is on the way"
    })
  }
  return msgs
}

/pubsub/subscriptionListener.go

A lifecycle of connecting on a websocket and disconnecting leaves at least 2 open goroutines. That full lifecycle should leave no leftover goroutines (unless it is maintaining an active subscription to the pubsub provider).

Not really sure if it is currently, honestly. But there are a bunch of different goroutines interacting with it, so should verify this.

A lot of tools like Kubernetes use health check endpoints, so we should research what those need to look like and implement it.

Most likely, we should have a default location for the endpoint (/ and/or /health) with the option for the user to specify their own. For the default, we should look at defaults for platforms like Kubernetes.

server:
  healthcheck: "/api/my-custom-healthcheck-location"

Currently it is just hardcoded into main.go

Maybe we throw it under server?

Like so:

server:
  port: 8080
  envfile: ./their/cool/path/.env

We can't test autotls on localhost, so we'll need to throw the project into a VM and try it there.

/pubsub/subscriptionListenerStandard.go

Not 100% sure how this should work, but I know tools like Caddy have methods of doing this automatically. We should probably do this in 2 steps, the second being a stretch goal:

1. Allow user to specify locations of certificate files in their config
2. [Stretch goal] Make server automatically configure TLS, with option for manual.