This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-07-14
Channels
- # announcements (3)
- # babashka (189)
- # beginners (157)
- # calva (5)
- # cider (5)
- # clj-kondo (7)
- # cljdoc (34)
- # clojure (61)
- # clojure-dev (2)
- # clojure-europe (42)
- # clojure-nl (15)
- # clojure-poland (1)
- # clojure-spec (5)
- # clojure-uk (6)
- # clojured (2)
- # clojurescript (31)
- # clojureverse-ops (8)
- # component (2)
- # cursive (41)
- # datomic (15)
- # depstar (44)
- # figwheel-main (9)
- # fulcro (14)
- # holy-lambda (1)
- # inf-clojure (13)
- # introduce-yourself (1)
- # jobs (1)
- # lsp (98)
- # malli (12)
- # off-topic (12)
- # pedestal (1)
- # polylith (3)
- # re-frame (51)
- # reitit (4)
- # releases (1)
- # reveal (5)
- # shadow-cljs (3)
- # tools-deps (56)
- # vim (12)
- # xtdb (36)
Is this advice on how to setup a websocket the recommended path? https://forum.datomic.com/t/websockets-from-ions/1255/4
Should we rely on :datomic.ion.edn.api-gateway/data
to 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.
@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.
Curious why the new Cloud https://docs.datomic.com/cloud/operation/compute-template.html#parameters uses yes/no for a boolean instead of true/false like the https://docs.datomic.com/cloud/operation/storage-template.html#parameters.
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.
@U1QJACBUM in yaml
if you write ClientApi: no
it will parse as :ClientApi false
https://yaml.org/type/bool.html
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](https://docs.datomic.com/cloud/operation/growing-your-system.html#monthly-price) 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.
No, but you only get valcache in the i3 family. https://docs.datomic.com/cloud/operation/growing-your-system.html#valcache