This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-05-10
Channels
- # babashka (35)
- # beginners (70)
- # bristol-clojurians (1)
- # calva (30)
- # cider (2)
- # cljsrn (203)
- # clojure (20)
- # clojure-australia (3)
- # clojure-europe (17)
- # clojure-france (7)
- # clojure-nl (4)
- # clojure-uk (8)
- # clojurescript (27)
- # code-reviews (19)
- # core-async (21)
- # cursive (7)
- # datomic (31)
- # defnpodcast (1)
- # duct (6)
- # emacs (3)
- # events (1)
- # helix (2)
- # honeysql (24)
- # jackdaw (2)
- # jobs (2)
- # jobs-discuss (13)
- # juxt (2)
- # lsp (21)
- # re-frame (45)
- # remote-jobs (2)
- # rewrite-clj (3)
- # shadow-cljs (13)
- # vim (1)
This might be tangential, but here鈥檚 a better way to solve the emacs ~ files
issue:
Tell emacs to create them in a dedicated directory (in this example ~/.emacs/savefile/
):
(defconst savefile-dir (expand-file-name "savefile" user-emacs-directory))
;; create the savefile dir if it doesn't exist
(unless (file-exists-p savefile-dir)
(make-directory savefile-dir))
Hello 馃檪 congrats on 0.4.0! It is a big release. I wonder with the addition to Selmer, if we could also consider adding this library from Yogthos for templating with hiccup? https://github.com/yogthos/hiccup-template
@neo2551 I think you could also just run that lib from source? It doesn't seem like a popular, widely used library yet, so including it seems pre-mature
Make sense :), but yes you could use from source indeed. I just find it more natural as a Clojure dev.
We already have hiccup included. This library seems to re-implement hiccup. Why do you need this lib?
Because for now, we generate hiccup through function calls as in (defn f [x] [:div x])
whereas with template, you can define a plain data structure [:div :data/x]
and then replace :data/x
with the hiccup-template/hiccup
function.
This allows you to serialize the template
so you could have your template in plain .edn file
when your logic is mostly replacing the fields with data.
does it make sense?
I would say we dissociate the act of writing the template and the function call?
thanks for your hinsight 馃檪
hindsight 馃檪
New static linux binary for testing: https://18553-201467090-gh.circle-artifacts.com/0/release/babashka-0.4.1-SNAPSHOT-linux-amd64-static.tar.gz
@borkdude Static binary is basically an executable with musl built in?
a static binary would be great
馃槈 that鈥檚 the plan
We're releasing an MIT-licensed project using babashka to to configure WordPress servers on EC2. The MySQL code is more robust than the examples (it can handle tabs), although not suitable for untrusted/arbitary input. Code's at https://github.com/staticweb-io/staticweb-open-wp/tree/master/static-wp-daemon/src/io/staticweb/static_wp_daemon
@borkdude Do you still want a MySQL/MariaDB example app? I just saw https://github.com/babashka/babashka/issues/387
@jshaffer2112 That was more about adding feature flags to babashka to support the mysql driver than about shelling out to the mysql binary.
I know
I'd much rather use JDBC than deal with the hellscape of mysql escaping
I'd be happy to write an app up if it would help
@jshaffer2112 I think honeysql (v2) can be of service here
ah yeah, it would be nice to have a reference example of how to do graalvm native with mysql
Then we can add support to https://github.com/babashka/babashka-sql-pods