This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-02-26
Channels
- # announcements (18)
- # aws (17)
- # babashka (19)
- # beginners (141)
- # calva (73)
- # cider (4)
- # clj-kondo (13)
- # cljs-dev (2)
- # clojure (97)
- # clojure-europe (6)
- # clojure-italy (5)
- # clojure-nl (1)
- # clojure-spec (25)
- # clojure-sweden (2)
- # clojure-uk (25)
- # clojured (3)
- # clojurescript (63)
- # core-typed (6)
- # cursive (23)
- # data-science (4)
- # datomic (74)
- # fulcro (19)
- # graalvm (18)
- # graphql (3)
- # hoplon (63)
- # jackdaw (1)
- # juxt (23)
- # london-clojurians (3)
- # meander (7)
- # off-topic (23)
- # om (1)
- # pathom (13)
- # pedestal (2)
- # perun (2)
- # re-frame (38)
- # reagent (3)
- # reitit (24)
- # shadow-cljs (91)
- # spacemacs (14)
- # sql (4)
- # tools-deps (8)
- # vim (3)
Spire is a new project building a pragmatic system provisioner as a clojure DSL. It can be used in place of older tools like ansible, fabric, capistrano and the like and works in a similar fashion. The first alpha pre-release (0.1.0-alpha.1) is up for people willing to test and experiment. Things could change and there is much documentation to write, so open tickets for whatever doesn't work or should be present. Available here: https://github.com/epiccastle/spire
@U1QQJJK89 Does it also make sense to use spire for when you are already on the instance? I’m thinking about an AWS userdata script. I can imagine the Spire dsl offers some benefits there over self-written install logic (e.g. even when written in Babashka)
You can use it to localhost
if you want. Although its primarily intended to "reach out" from your local workstation to remote machines. You can also make scripts with a shebang that will take arguments on the command line to do things or pick targets. https://github.com/epiccastle/spire/blob/master/doc/howto.md#read-the-launch-arguments
@U0FT7SRLP when you're already on the machine, you might also want to be looking at dad by @UBL24PLE6: https://github.com/liquidz/dad
Cool! Thank you both!
This is great - I'm currently refactoring some of our infra setup and out of frustration I had to put Ansible in a docker container, as managing python dependencies and packages is becoming challenging. I will try it out in my spare time and see if an equivalent of Ansible's docker_container
module is feasible 😉
Not sure if anybody is interested in this, but I was frustrated in the state of the marginalia documentation generator. I've forked it to include deps support, the unmerged pr for an open reader bug and theming support. https://github.com/captain-porcelain/sidenotes
Maybe give sidenotes a try and let me know if it is useful to you.
I haven't used cljdoc so far, so I can't say anything about the effort.
Here is an example: https://cljdoc.org/d/com.github.hindol/json-rpc.core/0.1.4-1/doc/readme Looks really clean. Kind of similar to how Github renders documentation.
Yes, it's really clean but quite different from what marginalia and sidenotes create.