I like the idea of projars, both as private hosting and as a marketplace
for commercial libs... again, my Datomic headaches influence my opinion,
but if commercial/internal libs could just be lein deps, it'd remove an
annoyance from my workflow.
As for clojars, I get wanting to keep it simple.
The past few teams I've been on have used variously S3, Nexus, and
Artifactory, and I wasn't especially happy with any of them. I think there
is a sweet spot of usability (for small/medium teams) and technical
capability that hasn't really been achieved by anything available. Of
what's
+1. Neither S3 or Archiva have worked out well for us long term.
On Monday, June 29, 2015 at 6:50:44 PM UTC-7, Daniel Compton wrote:
Hi folks
I wondered if one possible solution for ensuring Clojars long-term
viability and maintenance would be to use it to host private repositories
for
I think my company would be willing to pay a reasonable fee for private
Clojars repos, on something like the Github model? Not sure what the lein
overhead would be, I know grabbing Datomic Pro from non-Clojars with creds
is a motherf@#@#ing pain in the ass at times (but only in comparison to the
This is being done now with npm: https://www.npmjs.com/. Cost is $7/mo,
which seems reasonable.
On Tuesday, June 30, 2015 at 12:00:55 PM UTC-7, Jason Lewis wrote:
I think my company would be willing to pay a reasonable fee for private
Clojars repos, on something like the Github model? Not
Clojars is pretty much a one man show right now, but it currently
requires little time to maintain, and works fairly well. If it
supported private repos, the maintenance and support time would go up
considerably, and it would require some sort of business entity around
it. Doing that has been
Hi folks
I wondered if one possible solution for ensuring Clojars long-term
viability and maintenance would be to use it to host private repositories
for paying users as well? For many people, the thought of setting up and
maintaining Nexus or Archiva isn't an appealing one. I'm aware of the S3
