This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-01-07
Channels
- # announcements (2)
- # beginners (30)
- # calva (7)
- # cherry (15)
- # clerk (21)
- # clojure (1)
- # clojure-losangeles (12)
- # clojure-norway (1)
- # clojure-spec (3)
- # clojurescript (31)
- # conjure (2)
- # cursive (44)
- # datomic (13)
- # emacs (13)
- # honeysql (15)
- # hyperfiddle (7)
- # malli (2)
- # off-topic (17)
- # overtone (6)
- # reitit (7)
- # ring (58)
- # shadow-cljs (12)
- # squint (14)
- # tools-deps (14)
- # web-security (1)
- # xtdb (29)
As Sean alludes to in the message above, the next Clojure LA Meetup is Wed Jan 10 at 6pm PST, on XTDB2.0. More at https://www.meetup.com/los-angeles-clojure-users-group/events/298365620/
Here is the Zoom link for today's 6pm PST Meetup. https://intuit.zoom.us/j/96856676220?pwd=cjdlcmdmOXpieTVMRDJ3ZXZsRnpkdz09
Hey @U0AT6MBUL firstly, thanks for taking a look at XT things again! I'm not sure exactly what you're planning to look at, but I just took the liberty of pushing a few changes to the Learn XTQL Today tutorial (including a small bump to the deps) - hopefully that doesn't break anything if you pull the changes - I was keen to fix a few things and make some of the steps a lot clearer 🙂 We also have this https://www.jooq.org/sakila-based repository and in particularly a fork that contains a small HTMX application (using a tiny new Clojure REST framework): https://github.com/xtdb/sakila-playground/tree/htmx Hope you have a good session! Looking forward to catching the recording
Great. Thanks. Yes, we were going to go through the tutorial. We'll feed back any issues we notice.
Thanks to everyone who participated yesterday. It was a great exploration of XTDBv2. We didn't get that far into the tutorial this time, so we will likely continue the next time.
@U899JBRPF The one issue I noticed when setting up my environment was that in the file https://github.com/xtdb/2x-playground/blob/main/clojure/README.adoc copy-pasting the inline startup instructions did not work for me. I believe it is because somewhere in the chain two consecutive dashes are being replaced by a single em-dash. Perhaps a passthrough or literal passthrough is needed in the source?
Ahh, I'll blame GitHub's markdown rendering, but sorry about that! Will make sure it's fixed 🙂 thanks for mentioning
hey again @U0AT6MBUL was the session recorded out of interest?