This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-06-13
Channels
- # announcements (4)
- # babashka (72)
- # beginners (86)
- # biff (24)
- # boot (1)
- # calva (71)
- # cherry (1)
- # cider (8)
- # clerk (7)
- # clj-kondo (23)
- # clojure (78)
- # clojure-art (3)
- # clojure-austin (2)
- # clojure-europe (18)
- # clojure-hamburg (6)
- # clojure-nl (1)
- # clojure-norway (17)
- # clojure-uk (2)
- # clojuredesign-podcast (21)
- # clojurescript (17)
- # conjure (1)
- # cursive (18)
- # datahike (7)
- # datomic (7)
- # emacs (1)
- # etaoin (5)
- # events (1)
- # figwheel-main (4)
- # graalvm (37)
- # graphql (1)
- # humbleui (12)
- # hyperfiddle (10)
- # introduce-yourself (1)
- # jobs-discuss (7)
- # kaocha (1)
- # malli (5)
- # off-topic (12)
- # pathom (12)
- # practicalli (1)
- # reitit (11)
- # releases (2)
- # shadow-cljs (45)
- # tools-build (33)
- # wasm (18)
Hey so I just gotta say, it's a real delight developing with Electric! I have finally moved the code from my development bocks to a cloud-hosted IP so I can access it online. I noticed: if I do not use https and just use clear-text http: I can actually have hot-loaded changes on my production box. So now I have my IDE tapped into my box via SSH, and I'm live-coding the production box. CSS changes are instantaneous across all connected peers because of shadow-cljs I think. Granted, compilation time is slow at ~12-18 seconds per rebuild, but it's perfectly acceptable to code locally and push changes later if that gap is intolerable. last night I had my desktop, laptop, and phone all pointed to the same website, and as I implemented changes I watched all three of them update. It was quite a satisfying moment as a developer.
App is at 1600 lines and of the 16GB of ram, 4023MB are currently in use. I'm optimistic 16GB will be enough even for lots and lots of peers 😅
@U055PQH9R4M nice and very interesting work 🙂 Just for my understanding: You are running a shadow cljs server watch on you cloud server or how do you achieve hot code reload? And why is it not working with https? Shouldn’t it be possible to have nginx or any load balancer in front of your app and configure it as an ssl termination point?
I'm super curious to learn more about your setup! I'd be interested in a video demo of your environment and project, if you have the time to record such a thing. Also my only exposure to Electric code so far has been the tutorials so it'd be awesome to see how it works in an almost-prod situation!
I don't think the memory consumption is caused by electric's runtime fwiw, i would suspect the database query engine first (it may be reserving memory for future use?)
Where are you hosting @U055PQH9R4M
current mem use down from 4G to 1.5G after a reload, maybe it is the query engine? I'm using a "box" (an ip) at digitalocean.
@U023LKF2PQV it's all out of the box electric, not sure about shadow w/ https; maybe the default is to have it off, using cleartext http i get live compilations and immediate css upticks, you think it should also work this way with https? maybe, not sure.