Fork me on GitHub
Drew Verlee00:07:05

Is this advice on how to setup a websocket the recommended path? Should we rely on :datomic.ion.edn.api-gateway/datato have the requestContext and connectionId? If not, someone should drop a note there.


@U0DJ4T5U1 we are working on some advice given the changes in the new release. I’ll be sure to cross post when it’s ready.

Drew Verlee21:07:31

@U1QJACBUM that sounds great, ill be looking for it :0


does anyone have code handy to roundtrip transactor functions by reading them out of the database and then re-transacting them? need a way to take all existing db/fns and stick them in an in memory database for tests to use.


You mean like yes/no for client API?



ClientAPI 	Client API 	yes/no
Ions 	Ions 	yes/no

✔️ 2

Yeah. Just seems odd that a new naming scheme was introduced. Was wondering what the thinking was.


So I asked about this on standup and in summary "we like yes/no better, but have a principal of being backwards compatible." The joke was made, that the real question is why we didn't change reuse storage from true/false to yes/no. The original yes/no decision started when considering we were asking the user what they want for bastion/client-api/other considerations. We'll use yes/no going forward without changing that storage prompt.


Haha, thanks for answering 🙂


@U1QJACBUM in yaml if you write ClientApi: no it will parse as :ClientApi false I personally do not use YAML and hope to never use it. But it's very common in infrastructure/AWS to use yaml on things. Maybe is a good idea switch from yes/no to "yes"/"no" on docs


The [pricing table]( lists monthly prices. Does this mean that Ions now has a monthly cost even I scaled down all (my solo) instances?


You are still billed hourly. These monthly prices assume you are running for the entire month they are not a special new unit for pricing.

👍 2

Does the primary compute group need to run on i3.large instances?