This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-03-07
Channels
- # announcements (3)
- # babashka (28)
- # bangalore-clj (6)
- # beginners (91)
- # calva (14)
- # cider (7)
- # clojars (6)
- # clojure (24)
- # clojure-europe (3)
- # clojure-nl (5)
- # clojure-uk (134)
- # clojuredesign-podcast (1)
- # clojurescript (16)
- # cryogen (3)
- # cursive (3)
- # data-science (1)
- # events (1)
- # fulcro (7)
- # jobs-discuss (1)
- # luminus (4)
- # malli (1)
- # re-frame (7)
- # shadow-cljs (74)
- # spacemacs (23)
- # sql (6)
- # tools-deps (2)
I had been using lftp to selectively mirror artifacts from Clojars to an internal repo, but recent changes have broken directory listings (as they are now done with javascript). I have hacked around this for now, but now I wonder - what is the preferred method for creating a mirror (for my own internal use) of a subset of Clojars?
Hi Aaron! Sorry for breaking your workflow - we moved the repo to s3 (from Rackspace Cloudfiles) and lost the html index generation. Since it is on s3, you could use aws s3 sync
to synchronize a local copy. I would just ask that you don't run that more than once every 24 hours.
You may need aws credentials for that to work, but those credentials wouldn't need rights to that bucket - it's publicly readable.
Great Toby, I'll give that a shot. I will only have to run this when upgrading or adding dependencies for my internal team to use, which isn't that often - and I'm not after the whole repo either, just the packages and versions we know we're using.
This works perfectly - thanks!