This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (5)
- # babashka (35)
- # beginners (65)
- # braveandtrue (3)
- # calva (20)
- # cider (6)
- # clara (11)
- # cljs-dev (36)
- # cljsrn (64)
- # clojure (65)
- # clojure-europe (6)
- # clojure-germany (13)
- # clojure-italy (14)
- # clojure-nl (22)
- # clojure-spec (16)
- # clojure-sweden (6)
- # clojure-uk (81)
- # clojurescript (71)
- # conjure (120)
- # cursive (3)
- # datomic (10)
- # events (4)
- # figwheel (4)
- # figwheel-main (5)
- # fulcro (36)
- # ghostwheel (1)
- # graalvm (8)
- # helix (9)
- # jobs (4)
- # jobs-discuss (12)
- # kaocha (33)
- # leiningen (5)
- # luminus (1)
- # off-topic (24)
- # pathom (7)
- # rdf (4)
- # re-frame (3)
- # reagent (15)
- # reitit (11)
- # remote-jobs (1)
- # shadow-cljs (97)
- # slack-help (3)
- # spacemacs (23)
- # vim (15)
- # xtdb (35)
haha I recently joined Kotlin Slack its amazing how much cheerier this place is than there....
Aleksander - perfect fit. We use Spring Boot and Kotlin at work, a lot, i.e., nearly 99% of our production code is now Kotlin and Spring Boot (with my bit of Clojure thrown into the mix).
It's intesting too, that the Spring Framework itself is treating Kotlin as a first-class citizen.
The Spring Framework provides first-class support for Kotlin and lets developers write Kotlin applications almost as if the Spring Framework was a native Kotlin framework.
@minimal it seems to have been stalled for quite a long time... probably as a result of trying to be all the things
Cherry browns on a Filco Ninja. Excellent keyboard, but I work at home so there's nobody to complain about the clacking.🙂
hako royal clears with kailh box yellow for the mods, box royal for enter and halo true for space, kailh speed copper for backspace and esc
there's browns on the keyboard-that-just-broke, but I find them too easy to double-press
2015 is before they made a mess of it... there's enough travel to require a positive action, but not too much - and i gather the latest models have a sorted keyboard again
Hello everyone…. Quick question, as my Google-Fu is failing me…. Has anyone built a Docker Container, which they are prepared to share or share the Dockerfile for, for use with http://Forestry.io in order to do live preview of Cryogen websites..>?
Not heard of http://forestry.io before, but this v cool =)… I use cryogen myself and was thinking of using it four our company blog, forestry as an approach sounds great, please let me know if you move forward on this =)…
The only thing I could find was this: https://github.com/harlanji/tinydatacenter/tree/master/cryogen-docker Not 100% certain it’s cryogen blog, but I think so?
Hi @U0JUM502E 🙂 I ended up building my own, and it works! Sadly though, http://Forestry.io does not / cannot support Clojure “Front Matter” so the Clojure Maps we use at the top of Cryogen Docs can’t be configured into http://Forestry.io as templates and their editor TOTALLY fucks up the Clojure map at the top of the page. As such I could get it all working but only use the raw editor with no content / non-tech friendly interface for non-programmers and hence my hopes to use it for work are dashed until I can find the time to fork Cryogen to use YAML Front Matter instead of Clojure Front Matter, and now I say that I see how mad it sounds…
Anyway, if you wanted to look at my Docker container - ’cos you could use it locally if you can solve the inode / Docker Volumes issue for your editing toolchain, it’s here: https://hub.docker.com/r/maleghast/cryogen-forestry
It’s linked on the page, but the Public Github repo that drives the Container is here: https://github.com/maleghast/cryogen-docker
It’s all hooked up on Docker Hub so that new versions of Cryogen can be built by sending a blank commit to Github
Then on your local machine you’d run it like this: docker run -v [path/to/your/cryogen/site/root]:/opt/gensite -w /opt/gensite -p 8080:8080 cryogen-docker:latest lein ring server-headless 8080
it’s set to run on 8080 in that example ’cos http://Forestry.io needs that to be the exposed port
you can leave 8080 of the end and replace the
-p 8080:8080 with
-p 3000:3000 if you want standard
Like I said above, if your operating system alters the inode of the file you are editing, i.e. by saving a new one and replacing, in the way Linux and macOS do by default (at least with everything I’ve tried, including nano, so don’t believe what you read on the internet per se) then your files won’t update inside the container, making this whole thing fairly useless unless you like stopping and starting Docker containers…
I might be totally off the mark, but is this the issue? https://stackoverflow.com/a/55103896
It’s the other way around, but in both a cases you want to write to the underlying file?
I don’t think that this changes anything, the
-v … option on the command line should create a mount that binds a host location into the container.
The problem is that if you edit a file in that folder, in place, the inode of the file changes and Docker sees that as a security risk so it stays faithful to the old version of the file.
I remember, a few years back, a colleague at the BBC “solved” this, as in found a workaround, but I can’t remember how to do it.
IE, commit a forestry thing, then run an action to convert it? It’s a little bit roundabout, but for a first pass implementation it’s not too awful…