This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
Magnificent! With this update, I got Vim-Iced to play well with Biff just by adding com.github.liquidz/iced-nrepl{:mvn/version "1.2.474"} to the deps.edn and iced.nrepl/wrap-iced to the --middleware vector under :biff.tasks/clj-args in the config.edn :tasks map. I feel like a wizard!
1ha perfect!
I am not able to create a new project, even though I have java installed.
➜ ~ bb -e "$(curl -s )"
`java` command not found. Please install Java 11 or higher.
➜ ~ java -version
openjdk version "11.0.17" 2022-10-18
OpenJDK Runtime Environment (build 11.0.17+8-post-Ubuntu-1ubuntu220.04)
OpenJDK 64-Bit Server VM (build 11.0.17+8-post-Ubuntu-1ubuntu220.04, mixed mode, sharing)
➜ ~ uname -a
Linux predevi 5.15.0-56-generic #62~20.04.1-Ubuntu SMP Tue Nov 22 21:24:20 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
➜ ~ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04.5 LTS
Release: 20.04
Codename: focal I found that this was happening because of a https://github.com/jacobobryant/biff/commit/4d8b4cccbed70c4faff968172c17c40e4314652d that was pushed recently I had openjre installed, I also installed openjdk
hmm, maybe using javap wasn't an reliable as I thought then. I'll switch it back to the previous method, or perhaps use the old method as a fallback
Stack overflow, you've failed me again
The https://biffweb.com/docs/get-started/new-project/ clearly mentions JDK, it was my mistake that I tried running new-project with JRE.
does clojure work with just jre though? if so then jre should be sufficient for biff
(in which case I should probably update the requirements page)
This is now fixed
Just made another release with a couple additional small things. Notably, the Could not find namespace error when running bb tasks is fixed, hallelujah
https://github.com/jacobobryant/biff/releases/tag/v0.5.7
I'm, unfortunately, still getting that Could not find namespace error running bb tasks and bb --force dev doesn't seem to make a difference.
In that case there might be a typo? If you paste your bb.edn and contents of the files in tasks I could help doublecheck
Sure thing and thanks!
bb.edn
{:deps {com.d1kh/tasks {:local/root "tasks"}}
:tasks {dev com.biffweb.tasks/dev
format com.biffweb.tasks/format
clean com.biffweb.tasks/clean
deploy com.biffweb.tasks/deploy
soft-deploy com.biffweb.tasks/soft-deploy
refresh com.biffweb.tasks/refresh
restart com.biffweb.tasks/restart
logs com.biffweb.tasks/logs
prod-repl com.biffweb.tasks/prod-repl
prod-dev com.biffweb.tasks/prod-dev
hello com.d1kh.tasks/hello
post-receive com.biffweb.tasks/post-receive
run-cmd com.biffweb.tasks/run-cmd}}tasks I have this deps.edn
{:paths ["src"]
:deps {com.biffweb/tasks {:git/url "" :tag "v0.5.7" :sha "02b6bd543b76ad94d9e3afe9949191e0f37467f5"}}} tasks/src/com/d1kh/tasks.clj which is just this:
(ns com.d1kh.tasks)
(defn hello
"An example of a custom task. See ./tasks/"
[]
(println "Hello, Wrold."))"Hello, Wrold." because everything needs a little imperfection.hm, so you get the error if you run bb --force hello ?
I'm not seeing any typos
other than Wrold 🙂
It looks like bb --force hello works fine, but bb --force dev is still being stubborn.
well that's a bit of a head scratcher. I just double checked that bb dev works on a new project on the same commit you have in tasks/deps.edn, and that works.
what about another task in com.biffweb.task -- does bb --force run-cmd work?
Does bb hello work if you put this in your tasks.clj file?
(ns com.d1kh.tasks
(:require [com.biffweb.tasks :as tasks]))
(defn hello
"An example of a custom task. See ./tasks/"
[]
(println "Hello, Wrold.")
(tasks/dev))bb --version give you?Sorry, took a little nap there. I was running babashka v1.0.168, but I just upgraded to v1.0.169 and I'm still having problems with bb dev. bb --force run-cmd also can't find the namespace and neither can the new version of bb hello.
But here's a new wrinkle, I went and tried the bb dev in folder where I was working on the tutorial and that works just fine.
Just copied and pasted your files to my machine, got the error, and finally spotted the problem: you need to set :deps/root in tasks/deps.edn:
{:paths ["src"]
:deps {com.biffweb/tasks {:git/url ""
:tag "v0.5.7"
:sha "02b6bd543b76ad94d9e3afe9949191e0f37467f5"
:deps/root "tasks"}}} That was it! And that must've been the cause. Apologies for the hassle!
no problem!
I'm starting to lean away from using Fly as the recommended deployment platform.
• Unlike Digital Ocean, It doesn't come with managed services for postgres or s3. e.g. if you run postgres, you're just running it as a regular app, and thus you'll have to fix it if it crashes + worry about backups. (Both DO and Fly do have managed services for redis).
• It's actually a little bit more expensive. I forgot previously that in addition to containers, you'll also need to run storage volumes for XT. On DO a 1GB droplet is $6/month and comes with 25GB of disk space; on Fly a 1GB container + 25GB volume costs $9.45. Not necessarily a big deal, but a small tick against Fly nonetheless.
• The separate volume thing means there is an additional moving part/additional thing that has to be set up.
• Fewer pricing tiers on Fly. e.g. containers with shared cpus on Fly only go up to 2GB of memory; on DO they go up to 16GB.
• I think I can make deploying to DO pretty seamless if I publish an image for a pre-configured Biff instance, and maybe I can even get it on their 1-click app marketplace.
• I'm also feeling better about the VM experience now that the sudo: a terminal is required to read the password error has been fixed. I think the kinks are mostly all smoothed out now.
• I'm not sure if you can rsync stuff onto a Fly volume, which would be nice to have for developing-in-prod.
• It'd still take me a decent amount of time to get the Fly experience polished with docs and everything, so if I'm going to go through with that, I'd want the experience on Fly to be significantly better than it is on DO, which I'm not sure it would be.
So I think I'll shelve the Fly stuff for now, and I'll look into making a DO 1-click install image instead. And if anyone else wants to take the https://gist.github.com/jacobobryant/d3b2654c36161414a7b6a306b3f678b5 I wrote and make a tutorial for running Biff on Fly, I'll be happy to link to it in the docs 🙂.
That definitely works for me! The one-click deploy is probably my main wish and if that happens on DO then I have everything. No pressure from me, of course… my cup overruneth already. DO has great customer support and also a simple UI which I really appreciate. I also really appreciate their billing model with the add-funds-ahead-of-time model. That takes away the worry of accidentally running up a huge bill.
I have only tried DO and not left anything up for long but it isn’t that difficult - You do have to make sure you get the cheapest offerings and I think the managed postgres adds a bit. I’ll give it another try soon
It is ok to stick with filesystem persistence in prod as well. you'd definitely want to at least have DO's automatic weekly backups switched on. I'd be interested to set up an automated backup task and include it with Biff actually, e.g. have it backup the tx log + doc store to s3 every hour. DO's s3 clone is only $5/month, and there's enough space that you could use it for backing up as many apps as you want.
Fun fact for the thread: the least expensive droplet ($4 a month?) doesn’t work, but the next one up does. If remember correctly one needs 1GB of RAM.
I discovered that too 🙂 . I've since added a note to https://biffweb.com/docs/reference/production/ about that: > 1. Create an Ubuntu VPS in e.g. DigitalOcean. Give it at least 1GB of memory.