I want to create a websocket client serverside (to get data from a third party)… should I leverage what Biff uses for its magic, or bring in my own deps?

Being super lazy here, so feel free to ignore (because I could just try it and learn the steps): I want to build my million toy projects off one domain in DO… should I reflect that intent when answering Enter main namespace (e.g. com.example): or in any of the other entries? Any changes in the config files? Any tips on the DO configuration? I should mention the obvious… it’s subdomains I’m after (or a similar strategy). It’s all born out of a desire to create more ‘utility apps’ much like microservices… which perhaps suggests I shouldn’t be using Biff for them, but you never know when you’ll want the Biffy goodness.

By creating more small apps that rely on each other I can avoid bloat and also encourage reusability, I’m thinking, as well as stay focuses on the core functionality of each. CORS issues in local dev may be an unwanted result (which I’ve never really mastered avoiding).

But then again, CORS hell is largely avoided with Biff.

I think I recall there being possible tangles around ssl certs and subdomains and that relates to project setup.

I found this, but may be a bit orthogonal to my question (but it does sound cool). https://github.com/jacobobryant/biff/issues/58