This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-03-26
Channels
- # babashka (12)
- # beginners (53)
- # cider (6)
- # clj-kondo (2)
- # cljdoc (18)
- # clojars (6)
- # clojure (72)
- # clojure-europe (27)
- # clojurescript (85)
- # component (2)
- # conjure (4)
- # datalevin (43)
- # graalvm (8)
- # hyperfiddle (17)
- # lsp (72)
- # malli (5)
- # off-topic (1)
- # pathom (6)
- # perun (6)
- # polylith (10)
- # releases (1)
- # shadow-cljs (30)
- # xtdb (10)
Hi, I have a babashka/ clojure library for storing encrypted information. One interface to it is a command line tool wrapper. What are my options for keeping state between subsequent invocations of the command line tool? Ideally I'd like to keep state in memory since it's sensitive, but I think I am limited to disk/ environment variables? Perhaps I need to wrap the library as a pod so that it's a process. Would appreciate a pointer to a simple 'training' clojure based pod to use as a template for implementing the bencode interface etc. ps. I am aware of the stash pod but have written my own since I wanted a different cryptographic scheme for it.
For keeping state you can use the disk or a database. Stash also came to my mind. For a database, maybe the sqlite pod
Would babashka ignore :deps in deps.edn that's already built-in (like core.match ot httpkit)? I'm trying to make my bb scripts works in jvm and I want to make sure it's still free of java deps if it's used via babashka