Hey Brian et al,

We've looked into this quite a bit both for what we needed internally for 
our own CI at StrongLoop and as a product because a bunch of our prospects 
have asked about a private npm registry with "enterprise" features.  We use 
artifactory internally because it has great versioning, plays well with 
other CI (e.g. Jenkins) and does a decent job of storing binaries.

For folks who don't have artifactory from a Java based infrastructure who 
wanted a private registry we looked at www-npm and Reggie.  www-npm had a 
lot of moving pieces including CouchDB, ElasticSearch, Redis.  Reggie 
seemed to fit the bill for the use case of a private registry but it was 
deficient on a couple of key features centered around a subset of the npm 
protocol.  One of our engineers Miroslav added this subset and folks can 
read it about it here - 
http://strongloop.com/strongblog/deploy-a-private-npm-registry-without-couchdb-or-redis/
.

Reggie has simple flat file support for storing the packages, but what 
we're looking at is an integration to publish from artifactory into Reggie 
and for Reggie to have a URL hosted by artifactory.  This idea of building 
in npm support into a artifactory plugin is pretty intriguing though ;)

-a-



On Thursday, February 20, 2014 10:21:14 AM UTC-8, Brian Vanderbusch wrote:
>
> I've run into a similar situation, where my company has governance around 
> acquisition of Open Source Software.  So even thought we *have* interenet 
> connections, we really can't use them for npm.  We also have an artifactory 
> instance running with support for Maven, and I'm actually wondering if it's 
> possible to set up an npm mirror (with our own governance layer on top of 
> the couchDB) *inside* artifactory.  (It's a budget/precedent thing... 
> don't ask).  
>
> i have built the code for our specific brand of (Justice!) governance 
> around accessing/acquiring from npm where our registries are configured to 
> our local instance of an npm mirror, but it's only deployed at a level 
> where a few teams can access it and befit from it.  In order for me to 
> allow all the devs in our enterprise to use it, I have to have another team 
> that has that scope of support sign off on it.... and they just so happen 
> to have artifactory stood up with Maven.  So if I can find a way for 
> artifactory to pipe in updates from the global npm registry, then it's 
> considered a solution we already support, and I can actually stand up.
>
> so yeah... anyone taken a crack at, or have any thoughts on whether a 
> marriage between a couch based npm mirror and artifactory is possible?
>
> Thanks OP for this question! 
>
> On Monday, February 18, 2013 12:23:05 PM UTC-6, andy wrote:
>>
>> Apologies in advance because I've only glanced at this problem, but we 
>> work in a unique environment where we have no Internet connectivity.
>> So, with our Java apps, we run an instance of Artifactory on our LAN and 
>> load it by running an instance that is connected, which we then export and 
>> bring into the 'offline' instance. That gives us a sort of mirror of Java 
>> dependencies for maven and what not when we're developing.
>>
>> Is there anything like Artifactory for npm? Do I need to roll my own 
>> somehow (i.e. would a simple WebDAV server work or is it more complex)? 
>>
>> I've glanced at Mike's node-reggie idea so maybe that is a place to start 
>> (https://github.com/mbrevoort/node-reggie).
>>
>> We don't need anything fancy - just a way to add npm modules to a project 
>> without having to check them in or pass around a giant .zip copy with all 
>> possible repos...etc. (Right now I just have a "node_modules_for_work" 
>> folder where I load up a ton of modules, then I zip that up and bring it 
>> in.)
>>
>> I'm happy to go off and do some reading/digging, so links to similar 
>> ideas/attempts are appreciated. 
>>
>> Thanks,
>>
>> Andy
>>
>

-- 
-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to