yes use uberjar

ssh to droplet, run

java -cp target/app.jar clojure.main -m prod

Thanks, will give it a go.

@U09K620SG I got the XTDB Fiddle deployed to a Digital Ocean VPS droplet! 🙌 Took me all day grinding. First I pulled Electric fiddle into my project on a new branch. I got the fiddle running locally, learning to respect adding the prescribed XTDB_ENABLE_BYTEUTILS_SHA1=true Then focusing on deployment: I Complied the uberjar from the fiddle with the above command. Ubuntu on my droplet was complaining about being old and unsupported, but wouldn’t update. So I wiped the droplet and started from scratch, and had to fiddle with ssh keys. I wasn’t sure how much the system need to run a jar. So I installed just java and tried to run the jar at root. Nothing. So I walked though the Biff https://github.com/jacobobryant/biff/blob/dev/example/server-setup.sh script, running the parts that looked meaningful to a clean build. I left out nginx thinking that would be handled by the jar.. Still nothing. So I set up nginx and a certbot, then it would load, but not showing any content. I needed to add the env var in the right spot on the jar call XTDB_ENABLE_BYTEUTILS_SHA1=true java -cp app.jar clojure.main -m prod Up and working!! Reactive multiplayer feels magical! ⚡ I did get one crash with client_loop: send disconnect: Broken pipe . My internet connection went out about the same time. Will set up systemd to auto-reboot..? In retrospect I was in a bit over my head, and probably should have just gone with docker and a service to save time. But i did get some hard won learnings and confidence flexing on the devops side (a weak spot for me). I’m glad to have the electric fiddle repo as a launchpad. I was tempted to go with the starter repo, but I figured this was more likely to be up to date and provide more working example code. Thanks for the considerations on that.

are you saying our xtdb fiddle is missing a readme step or something? sorry you had to debug that, it doesn’t seem like electric issues, these all look like xtdb issues

xtdb fiddle - https://github.com/hyperfiddle/electric-fiddle/tree/main/src/xtdb_demo

it has the env var

fwiw the starter app is up to date as of friday or so, but we don’t intend to maintain database specific starters outside of the fiddle repo

oh i see, you didn’t know how to install clojure cli

I think the fiddle, and the documentation is fine. The environmental var was in the documentation. That was all about me noodling through the deployment process outside of electrics concerns.

I have the closure CLI command installed locally. I’m not sure if I installed it remotely. I was under the impression and I didn’t need that to run the Uber jar.

Just a little journal about me learning to deploy an Uber jar.

There is a little variation on where the environment variable goes in the clojure CLI, versus the Java commands. Thankfully, I got a error read out in the consul, when it wasn’t included properly, when I tried to run the jar in production. And that alerted me to get it right

you do not need clj for uberjar, sorry

The datomic browser uses the datomic peer api. We haven’t tried to adapt it to datomic cloud.

Oh ok, thanks! are there any plans to support it?

I’m not sure, I’ll ask

We are not planning to adapt datomic-browser to datomic cloud. But if you want to do so, there is datomic-cloud compatible code in our https://github.com/hyperfiddle/electric/tree/master/src/contrib.

thanks! i’ll take a look

I have "app navigation" where I have it look at the first subfolder in the url ... right? localhost:8080/browse for example

However, the hyperfiddle examples application overrides this on page refresh....

wants things to conform to for example (ShompMain)

question... how can i stop the examples app from reading the URL location and changing it? I will look in the code, this is not helpful for developing routing/navigation #2¢

So yeah 😅 can someone help me find out how I can make the fiddles manager not override navigations?

I am stoked at the ability to now mint prod versions easily, I think that's cool, but I'm really not clear on how I can remove some of the scaffolding around the examples browser so I can get back to messing with the navigation myself. Since in the application people ought be able to click nav buttons and have it reflected in the location bar / url.

Ah ok I found where this is happening:

(ns electric-fiddle.main
  (:require
   [hyperfiddle :as hf]
   [hyperfiddle.electric :as e]
   [hyperfiddle.electric-dom2 :as dom]
   [hyperfiddle.router :as r]
   [electric-fiddle.index :refer [Index]]
   ))

(e/defn NotFoundPage [& args] (e/client (dom/h1 (dom/text "Page not found: " (pr-str r/route)))))

(e/defn Main [ring-req]
  (e/server
    (binding [e/http-request ring-req]
      (e/client
        (binding [dom/node js/document.body]
          (r/router (r/HTML5-History.)
            (dom/pre (dom/text (pr-str r/route)))
            (let [route       (or (ffirst r/route) `(Index)) ; route looks like {(f args) nil} or nil
                  [f & args]  route]
              (set! (.-title js/document) (str (some-> f name (str " – ")) "Electric Fiddle"))
              (case f
                `Index (Index.)
                (r/focus [route]
                  (e/apply (get hf/pages f NotFoundPage) args))))))))))

And I'm wondering what I ought to do to.... take this over elegantly 😅

Also, the "not found page" is optimistic and never evaluated, I think. Because it has to conform to the very specific formula for what a page is, otherwise it's not ISeqable and the "page not found" page is actually a name and the word nil so... just something to keep in mind. Wrenching out this plumbing is taking some effort )

NVM noticing a new electric-starter-app

yes use starter app

Are you saying there is a conflict between the default client side routing and your custom server side routing?

Everything I said is irrelevant ) Was gutting the demos app ... and there is no need for that now