clojars

http://clojars.org discussion and “support”, see http://status.clojars.org for status.
andrewboltachev 2016-10-17T12:47:27.000310Z

Hello. Does it look like valid traceroute for http://clojars.org?

andrewboltachev 2016-10-17T12:48:22.000312Z

The problem is that all my lein deps, lein uprgade or even e.g. lein new figwheel ... commands basically hang

2016-10-17T12:51:01.000313Z

@andrewboltachev: that trace looks very similar to what I get (stars past http://core7-aggr403b-9.iad3.rackspace.net), but lein deps works fine

2016-10-17T12:51:27.000314Z

I don't think lein upgrade hits clojars, so that might be a clue that something else is going wrong on your end

andrewboltachev 2016-10-17T12:51:29.000315Z

I mean, when you download new stuff, ofc

andrewboltachev 2016-10-17T12:51:59.000316Z

The thing is it's on both my local machine (Kirov, Russia) and server (Amsterdam, The Netherlands)

2016-10-17T12:52:10.000317Z

right, I removed deps from my ~/.m2 and ran lein deps

2016-10-17T12:52:48.000318Z

hmm, can you try the new CDN-fronted <http://repo.clojars.org|repo.clojars.org> and see if that behaves the same?

2016-10-17T12:53:03.000319Z

you'll need to add the following to ~/.lein/profiles.clj:

2016-10-17T12:53:26.000320Z

:repositories [["clojars" {:url "<https://repo.clojars.org>"}]]
:plugin-repositories [["clojars" {:url "<https://repo.clojars.org>"}]]

2016-10-17T12:53:31.000321Z

in your :user profile

2016-10-17T12:54:08.000322Z

you'll get a warning from lein about having repos in the :user profile, but you can ignore that for now

andrewboltachev 2016-10-17T12:56:16.000323Z

I haven't had this file btw:

andrewboltachev 2016-10-17T12:56:31.000324Z

{:user {
        :repositories [["clojars" {:url "<https://repo.clojars.org>"}]]
        :plugin-repositories [["clojars" {:url "<https://repo.clojars.org>"}]]

        }}

andrewboltachev 2016-10-17T12:56:42.000326Z

should this be valid?

andrewboltachev 2016-10-17T12:57:13.000327Z

Well, with this, I have:

2016-10-17T12:57:18.000328Z

yes, that should be correct

andrewboltachev 2016-10-17T12:58:11.000331Z

18 sec for 14.6M sounds quite serious

2016-10-17T13:00:04.000332Z

that doesn't use clojars though: https://github.com/technomancy/leiningen/blob/master/bin/lein#L73

2016-10-17T13:00:21.000334Z

so adding the CDN repo should have made no difference

andrewboltachev 2016-10-17T13:00:39.000335Z

yep, I've had GitHub also working with delays for me

andrewboltachev 2016-10-17T13:01:15.000336Z

Okay, either I have VPN or not, my physical connection stays the same

andrewboltachev 2016-10-17T13:01:27.000337Z

So that might be it's issues

andrewboltachev 2016-10-17T13:02:43.000338Z

thanks @tcrawley and I would check everything more carefully. This CDN should be helpful btw

2016-10-17T13:03:01.000339Z

glad to help

mpenet 2016-10-17T13:31:54.000340Z

is it feasible to run private clojars install now?

mpenet 2016-10-17T13:32:07.000341Z

wondering if I could swap archiva with clojars-web

2016-10-17T13:37:43.000342Z

@mpenet: possible? yes. feasible? probably not. It would be a lot of work to set up

2016-10-17T13:38:15.000343Z

we've been working on an ansible setup for it that would ease that, but there are still lots of clojars.org-specific bits in there

mpenet 2016-10-17T13:52:45.000344Z

alright, anything in particular (I might be able to help with some of it maybe)?

2016-10-17T14:52:10.000345Z

@mpenet: we haven't given specific thought to where we need to make changes to support private instances, we've been focused first on getting a reproducible setup, so don't have a list of what needs to happen. You are welcome to take a look at what you have to see what would need to change if you like: https://github.com/clojars/clojars-server-config

mpenet 2016-10-17T15:54:25.000347Z

one of the big missing piece might be auth on the artifacts. if I am not mistaken now they are served via nginx directly

mpenet 2016-10-17T15:57:54.000350Z

then maybe it makes sense to map auth on these to user/groups credentials (thinking out loud)

mpenet 2016-10-17T15:59:03.000351Z

also another question would be do we want to allow auth per artifact or is it an on/off switch that applies to the whole instance

mpenet 2016-10-17T16:00:41.000353Z

serving the artifacts via nginx is a good thing, that's where all the pressure is and it's the perfect solution doing the heavy duty work, I don't know if it can be reconfigured "dynamically" for the auth part

mpenet 2016-10-17T16:05:57.000355Z

maybe with lua + redis (for instance). But yeah, I know, it's another dependency ...

mpenet 2016-10-17T16:08:40.000357Z

cool stuff: http://nginx.org/en/docs/http/ngx_http_auth_request_module.html

mpenet 2016-10-17T16:09:02.000358Z

anyway, I ll stop flooding for now and look into this a bit on my free time 😆