This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-05-06
Channels
- # bangalore-clj (2)
- # beginners (24)
- # boot (18)
- # cider (21)
- # cljs-dev (11)
- # clojars (3)
- # clojure (99)
- # clojure-brasil (1)
- # clojure-dusseldorf (2)
- # clojure-france (9)
- # clojure-greece (3)
- # clojure-russia (1)
- # clojure-spec (5)
- # clojure-uk (5)
- # clojurescript (205)
- # core-logic (2)
- # cursive (24)
- # datomic (13)
- # figwheel (1)
- # gsoc (1)
- # jobs (1)
- # jobs-discuss (7)
- # lambdaisland (5)
- # leiningen (4)
- # om (2)
- # pedestal (2)
- # proton (2)
- # re-frame (7)
- # reagent (5)
@flyboarder simply adding a shutdown hook doesn't seem to cut it, I assume (given the namespace in which add-shutdown-hook!
resides) that I'll have to perhaps make a pod ?
And in more general terms, if anyone has an example of making a new pod with shutdown hooks (and what the hell that actually even implies), I'd be grateful
@pseud checkout the boot-nodejs serve task, uses shutdown hooks to kill rogue nodejs threads
⚠️ boot-semver
now supports Continuous Deployment v1.5.0
⚠️
https://github.com/degree9/boot-semver
@flyboarder awesome that you can push snapshots like this, but is it pushing on every file change?
I dont recommend it, but the goal was to solve the repeated use of the version task in pipelines
Is it possible to do it ? A conditional watch it is not possible but you could maybe read meta from the version file
im not sure it is, I think the correct way to store mutative data is in the env map