This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-06-06
Channels
- # aleph (15)
- # beginners (40)
- # boot (14)
- # cider (90)
- # cljs-dev (132)
- # cljsrn (25)
- # clojars (7)
- # clojure (188)
- # clojure-chicago (4)
- # clojure-dusseldorf (1)
- # clojure-greece (9)
- # clojure-italy (43)
- # clojure-russia (16)
- # clojure-sg (7)
- # clojure-spec (39)
- # clojure-uk (81)
- # clojurescript (170)
- # component (5)
- # core-async (7)
- # cursive (49)
- # data-science (65)
- # datascript (3)
- # datomic (27)
- # graphql (3)
- # hoplon (4)
- # instaparse (56)
- # klipse (129)
- # leiningen (1)
- # lumo (28)
- # off-topic (4)
- # om (15)
- # onyx (54)
- # overtone (7)
- # pedestal (7)
- # re-frame (9)
- # reagent (72)
- # ring (33)
- # ring-swagger (2)
- # spacemacs (1)
- # untangled (19)
- # vim (2)
- # yada (12)
@danielcompton sweet thanks for the input
@alex-dixon you might consider #beginners as well as it’s more active. Also mention what guide you have followed so far and what broke 🙂
@danielcompton thanks, great to hear Clojars is doing The Right Thing ™
@danielcompton are these versions tracked in the database at all currently?
If they’re not stored in the DB then maybe a link to the /repo page of a snapshot version is a reasonable solution?
@martinklepsch Thank you. I received help in #clojure and was able to deploy 🙂 The solution I received and problems I encountered are being discussed here https://github.com/clojars/clojars-web/issues/643
Ah yes, we don’t keep the full version number for snapshots. Not sure if better to link to repo page (bit overwhelming), or to store last version in db