This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-08-02
Channels
- # announcements (6)
- # beginners (35)
- # calva (5)
- # cider (3)
- # clj-http (1)
- # clj-kondo (52)
- # clojure (51)
- # clojure-conj (2)
- # clojure-europe (28)
- # clojure-losangeles (1)
- # clojure-norway (8)
- # clojure-uk (2)
- # cursive (12)
- # datalevin (2)
- # datomic (38)
- # emacs (7)
- # events (5)
- # gratitude (1)
- # humbleui (7)
- # hyperfiddle (23)
- # jobs (1)
- # off-topic (6)
- # portland-or (1)
- # rdf (3)
- # releases (2)
- # xtdb (3)
What's the favorite way to deploy a production Electric based application? Say you were ready to deploy the Electric XTDB demo as a production site, is there a straight forward way to deploy to something like http://Fly.io? Do you deploy the database together with the application or separately?
digital ocean is the most straightforward way - database and java app on same machine
graduate to aws
We’ve done this on Fly. DB and app on the same server, with their postgres thing as durable storage.
I know this isn’t the priority of Electric but it would be super nice to be able to front end only build. I prefer Electric over React for developing the front end and sometimes “webapps” live inside of other ecosystems like Telegram mini apps. Contemplating a small gig but my only pause is having to step away from this experience ⚡
I believe this is in the plan for Electric v3. Check out https://clojurians.slack.com/archives/C7Q9GSHFV/p1722431682180419
Is this true @U09K620SG? I thought I saw you say it would be easier to do. But will it be possible without being hacky?
it is done
in principle
Hmm. I would like to test drive.
Anyone working on an internal knowledge thingy in electric clojure? Some starting points from a thread in offtopic https://github.com/nextjournal/clerk https://github.com/zeitstein/brimm
https://github.com/lumberdev/tesserae seems like a pretty neat starting point for such a thing (https://www.youtube.com/watch?v=nEt06LLQaBY&feature=youtu.be)
I sketched out my thoughts on a PKM in this repo: https://github.com/subspace-ai/subspace/tree/master But tesserae looks pretty great, am thinking of basing v2 of subspace on tesserae. Will maybe sketch out the UI once electric v3 is out.

Some starting points from a thread in offtopicthanks for mentioning this thread! it's got a lot of good opinions and ideas in it. For ease of reference it's here: https://clojurians.slack.com/archives/C03RZGPG3/p1722439345938229 And now I'm wondering whether Slack will add backlinks someday 😅 for more non-Electric-specific PKM chat feel free to use #tools-for-thought
is there a way to get a missionary flow of new xtdb dbs while not using the in-process node? I want a persistent xtdb (lmdb backend) and to use electric with it. Thttps://github.com/hyperfiddle/electric-fiddle/blob/28b875d3eaa77f2d8b4716f383ba8f5ed2e1b92e/src/xtdb_demo/xtdb_contrib.clj#L6 still says it only works for in-process node
just tried it with lmdb node, and it worked fine! is this comment worth updating? did something change?
in-process != in-memory
- LMDB counts as in-process too. The example for being out-of-process would mean using XT's HTTP stack (the server and client modules)
gosh, you're right...I've been writing so much SQL recently that I initially wrote in-process <> in-memory
what does "LMDB" mean
as in using the popular embedded key-value store LMDB as the index storage for XTDB v1 (and potentially also for tx-log + doc-store components), see https://v1-docs.xtdb.com/storage/lmdb/