This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-06-03
Channels
- # aws (12)
- # beginners (12)
- # biff (10)
- # calva (1)
- # cider (10)
- # cljfx (1)
- # clojure (2)
- # clojure-conj (1)
- # clojure-europe (25)
- # clojure-madison (1)
- # clojure-nl (1)
- # clojure-norway (12)
- # clojure-sweden (4)
- # clojure-uk (6)
- # datomic (11)
- # dev-tooling (3)
- # emacs (5)
- # gratitude (1)
- # introduce-yourself (7)
- # java (3)
- # jobs (1)
- # london-clojurians (2)
- # lsp (23)
- # off-topic (4)
- # practicalli (9)
- # quil (6)
- # re-frame (3)
- # reagent (4)
- # remote-jobs (1)
- # ring (1)
- # shadow-cljs (18)
- # squint (67)
- # tools-deps (5)
- # xtdb (4)
- # yamlscript (12)
hi all! I'm having trouble deploying to http://fly.io. I found this repo but I'm not sure what to do with the work I did following the tutorial. I launched and deployed the Dockerfile using the flyctl cli but my VM's just stop after a few minutes @foo I found this repo that you made https://github.com/jacobobryant/biff-docker2 but I'm struggling on how to apply it
Hi--can you see if fly has any deployment/runtime logs? the Dockerfile that comes with new projects should work on Fly; I've deployed it there before. Let's see... I think the default RAM for fly apps is 500m, you'll need to change it to 1gb. other than that I don't think you'll need to do anything special to get the app running. you'd want to set up fly postgres for persistence after you've got the app running.
besides that, I'll also note that every time I've tried Fly I've ran into weird bugs... last time I got the app running and could log in, but after that, trying to go to the app in another tab always had some kind of networking/DNS error. 🤷
so let me know how it goes! I've been sticking with digitalocean for now but have been watching Fly with interest from the sidelines
In electric there have been some http://fly.io deploy demos, and I successfully followed one. But I was warned to stick to a more classical host (DO) because of some anomalies that others experienced.
yeah--I think Fly is the future, just not so sure about the present ha ha
I think traditional VMs are a bit better fit for Biff anyway, at least in the early solo developer stage where you only run on a single machine. you can deploy faster + with zero downtime via clj -M:dev soft-deploy
, and you don't have to set up checkpointing for XTDB (without checkpointing, if you're deploying with containers, you'll have to wait for XTDB to re-index the entire transaction log whenever you do a new deploy--but with DO/regular VMs, the index persists between deploys).
Did you see this recent tutorial? https://bogoyavlensky.com/blog/deploying-full-stack-clojure-app-with-kamal/ Looks like Kamal is a deployment config library to make a heroku-like experience, portable to different cloud hosts. https://kamal-deploy.org/ > Feed the config file a list of IP addresses with vanilla Ubuntu servers that have seen no prep beyond an added SSH key and you’ll be running in literally minutes. overkill for Biff?
I hadn't read the article, though I see Kamal is still using Docker, which yeah, I think would be overkill for Biff--`server-setup.sh` works pretty well IMO, and the JVM already has good dependency management/isolation built-in.
great! thank you for all the messages! I got a little busy with work. I'll go through and try them out, thank you!!