Cloning Herd

[Luke deGruchy]

I've attempted to clone ceylon-herd following all the instructions in the README on the github project page.   I was able to make my user admin, access the site over http from another computer on my network, and publish a module that doesn't import any other module.

Where I've had problems is in publish a module that imports another module outside of my Herd instance, there's an error with my upload.  It complains that the module can't be found in my repo.   In this case, I tried to import ceylon.collection/1.1.0.   There's a link to Resolve From Maven Central, which fails.  This is what I see in the Play output:

Looking up module in Maven Central at: http://repo1.maven.org/maven2/ceylon/collection/1.1.0/collection-1.1.0.jar.

Is the idea that I need to republish those modules onto my repo, or is there some configuration step that I'm missing (after RTFA and Googling, I'm not able to find it).

[Luke deGruchy]

Sorry, but I'm going to bump this.   I'm just wondering if this is a missing feature or I need to configure something.

[Stephane Epardaud]

Hi, and dreadfully sorry for the late answer, every time I remember to answer I'm away from the computer and forget when I'm in front of it.

So yeah, right now private Herd deployments can't delegate to other Ceylon repos, and that's fine for the main repo, but frankly lame for other repos, like your deployment. We should definitely add that feature, and if you want to try to add I can help :)

--
You received this message because you are subscribed to the Google Groups "ceylon-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ceylon-users...@googlegroups.com.
To post to this group, send email to ceylon...@googlegroups.com.
Visit this group at http://groups.google.com/group/ceylon-users.

To view this discussion on the web visit https://groups.google.com/d/msgid/ceylon-users/360e7733-58df-47f9-99c7-eb72e1216552%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Stéphane Épardaud

[Luke deGruchy]

Hi,

No problem on the late reply.  I know how busy you guys are.

What's the open issue for this?   Is it https://github.com/ceylon/ceylon-herd/issues/196 ?

What would be the general approach to implementing this (cloning the main repo, forwarding requests to it, etc)? How difficult would be this be to implement, what's the scale of the effort involved?   

I log into gitter once in a while so you might be able to catch me there.

[Stephane Epardaud]

Yes that's the issue. I figure it's more or less a copy of the current "resolve from Maven" upload feature, so it should be easy.

To view this discussion on the web visit https://groups.google.com/d/msgid/ceylon-users/9eff62bf-1fae-4785-9485-003a32e3e2f5%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Stéphane Épardaud

[Tako Schotanus]

Well it would probably be more than that, right?

I mean the Maven support is only used when uploading a new module, while this could be useful also for someone trying to use a module that's not (currently) available in the repository but can be found in other, proxies, repositories. It would then function like a kind of cache for those repositories.

-Tako

To view this discussion on the web visit https://groups.google.com/d/msgid/ceylon-users/CAKU9E9vptfVhGStuNaVt3U09-7cFLzDY1BdXi256B631X43C7w%40mail.gmail.com.

[Stephane Epardaud]

I don't see why we'd have to proxy other repos. The users can do that, and indeed Herd is always included so anything not resolved from your own Herd instance will be resolved from the main one.

To view this discussion on the web visit https://groups.google.com/d/msgid/ceylon-users/CAOJRyvprpbmRmLCaAQ5M%3DTG_%3Djr9J%2BCoHZFyQ%3D-o1hA0uBOJpQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Stéphane Épardaud

[Stephane Epardaud]

I mean, there are various well known proxies that can be used for caching if that's what you want… I don't see why Herd should try to reinvent caching.

--

Stéphane Épardaud

[Tako Schotanus]

> The users can do that, and indeed Herd is always included so anything not resolved from your own Herd instance will be resolved from the main one.

Not everybody has direct internet access, in fact I've worked on several projects where the client didn't allow any direct external connections (Banks are especially prone to do that) and they'd install their own Maven servers that would then proxy to the official external Maven repo.

It also means that you can configure all the needed (third-party) repos in one place and everybody can use them automatically without having to know anything about them.

> I mean, there are various well known proxies that can be used for caching if that's what you want… I don't see why Herd should try to reinvent caching.

If you're positive that a normal proxy (let's say Apache) can do all what I described above okay, but the Maven server implementations that I know of all include the option to proxy to external servers.

-Tako

To view this discussion on the web visit https://groups.google.com/d/msgid/ceylon-users/CAKU9E9tP9OmSN9LuamhuAXxnnxomR7J%3DatkYYtQY5JyNeAxENA%40mail.gmail.com.

[Stephane Epardaud]

Let's put it this way: it's trivial to add support for what Luke needs. Turning Herd into a proxy is not trivial at all, and is redundant with the job of proxies in most cases, so I really hope he does not need that ;)

To view this discussion on the web visit https://groups.google.com/d/msgid/ceylon-users/CAOJRyvqSjRJxzdB9gQf3fYsPAby8DAeTpQzrSVJ9oPivATe8GA%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Stéphane Épardaud

[Luke deGruchy]

Personally, my needs are very simple.  I would like to publish modules from my workstation to a Herd repository on a FreeBSD server.  On the server I could then run a simple webapp using modules common to my local network.

Tako's point about corporations using proxies is valid insofar as promoting the Ceylon ecosystem to the enterprise, but that could that not simply be captured by another github issue?