Clojurians Log v2

Good news (I think). First stab at a aws-api pod. Calling it a day. Happy new year!

S3 requests work as well. only aws/doc gives some problems (it prints to standard out). Will look at it later

One last time this year! @rahul080327 and I are happy to announce the sqlite3 pod! https://github.com/babashka/pod-babashka-sqlite3 Use sqlite from babashka. The pod is self-contained, no need to install sqlite3 on your system. Implemented in golang and uses transit for communication. Even blobs work.

@thomas.ormezzano Btw, we used the go transit library for the above to deal with the bytes over the wire, it worked well

Just a silly question, but would it be possible to use pod with traditional Clojure applications?

I would be interested into linking this go app with Clojure to support "dqlite"

https://github.com/canonical/go-dqlite

dqlite is a distributed sqlite from Canonical

@neo2551 Yes, you can use pods with the JVM

Interesting 🙂

you will need to use the pods library: https://github.com/babashka/pods

I asked before, but maybe something has changed then, is there jsch pod or something?

What would a jsch pod do for you - can you describe the use case?

I’m looking for ssh port forwarding solution. Last time I built my own binaries by compiling some clojure code with graalvm. Maybe I’m wrong calling it pod, basically I want something that allows me to stay within bb script and use jsch

Can you sketch what an example call would look like?

Last time someone asked about this I replied: what about shelling out to ssh using babashka.process - is there something that you could do with jsch which cannot be done that way?

There is a bb-like project (based on sci as well) which uses stuff like jsch under the hood: https://epiccastle.io/spire/ So I'm pretty positive that this can work, I just don't know the requirements that well

I think what I want is pretty close to clj-commons/clj-ssh just tried to run it with bb but it’s not working out of the box. Yes, shelling out is possible, but I wanted to abstract the platform https://github.com/clj-commons/clj-ssh

right

One example where shelling out is not a good option is native macOS apps. In sandbox you don’t have permission to run arbitrary binaries but only those you provide within your app

A pod is also loading an external binary btw. It's comparable to shelling out, it's just more structured

Right so I’m thinking this structure is quite helpful for bundling

thank you for your helpful responses @borkdude and happy new year! :)

I made an issue here: https://github.com/borkdude/babashka/issues/694 I'm willing to set up a private skeleton project in the babashka repo and invite you for collaboration if you want

To get things started

Thanks, the same to you!

Awesome, thanks again!

Small dev tip: You can test the pod from the JVM without going native:

(pods/load-pod ["clojure" "-M" "-m" "pod.babashka.buddy"])

But you probably already figured that out ;)

What is your github id?

RomanTsopin

Added you to https://github.com/babashka/pod-babashka-ssh

@jeroenvandijk I created the repo here and gave you write access. If you want you can continue over there: https://github.com/babashka/pod-babashka-aws Currently I'm getting this:

$ bb test.clj
----- Error --------------------------------------------------------------------
Type:     clojure.lang.ExceptionInfo
Message:  Cannot find resource cognitect/aws/s3/service.edn.

Feel free to poke me. I also added @rahul080327 and will add more people if they want, until there is a release that's suitable to make public