Alex, I think that's an awesome idea. But...a) I stink at node b) probably don't have time to devote to help beyond complaints/a list of what I'd like to see c) I'm full of excuses.
There is Mike Brevoort's node-reggie - https://github.com/mbrevoort/node-reggie (I keep name dropping that hoping he'll appear out of thin air with a bunch of commits that finish it up :) ), maybe that can be of some use. I'll definitely keep my eye on your repo and maybe I can help out at some point. andy On Wed, May 22, 2013 at 9:04 AM, Alex Kocharin <[email protected]> wrote: > Andy, > > > > I would prefer to use some sort of proxy/cache, were we only pull mods > we need (ala Artifactory or Nexus in Java land) but I hadn't really seen > anything like that. > > Well... what do you think about creating one? :) > > I started a project on github - https://github.com/rlidwka/npmrepod , and > described how I would like to see this thingy. There's no code there, but > it's expected to change soon enough. The idea was around for 6 months or > so, and I more or less know how it would work (except for authentication > and access rights...). > > Any thoughts on this? > > > -- > // alex > > > On Sunday, May 19, 2013 2:39:40 AM UTC+4, andy wrote: > >> Alex, >> Response inline. :) >> >> Sent from my iPhone >> >> On May 18, 2013, at 10:45 AM, Alex Kocharin <[email protected]> wrote: >> >> >> Why do you want replication at all? I was thinking about it for myself >> recently, but I found out that there're lots of libraries you won't ever >> use. >> >> >> So isn't it better to write something like proxying repository server >> that would host your private projects, but proxy all other requests to npm >> central repository (with caching of course to avoid heavy load)? >> >> We don't have any other choice, sadly - we have no network connectivity >> to npm central where we have to develop from. >> >> So our thought was to replicate against npm while connected, then take a >> copy of couch/npm (even with a bunch of stuff we won't use) offline. >> >> I would prefer to use some sort of proxy/cache, were we only pull mods we >> need (ala Artifactory or Nexus in Java land) but I hadn't really seen >> anything like that. Ill have to check out shadow-npm. >> >> Andy >> >> >> On Tuesday, May 14, 2013 7:16:51 AM UTC+4, andy wrote: >>> >>> Based on the awesome feedback I got from https://groups.google.** >>> com/d/msg/nodejs/sX4mbsRPwls/**WtDDE-To2o4J<https://groups.google.com/d/msg/nodejs/sX4mbsRPwls/WtDDE-To2o4J>, >>> we tried replicating the npm repo so we could use it in an offline >>> environment. >>> >>> We're essentially following the instructions at http://clock.co.uk/tech- >>> **blogs/how-to-create-a-private-**npmjs-repository<http://clock.co.uk/tech-blogs/how-to-create-a-private-npmjs-repository>but >>> replication fails after syncing about 17k documents. >>> >>> We've tried reinstalling couch (found one issue that suggested using a >>> patched version of SpiderMonkey) but the same thing keeps happening, even >>> after restarting replication several times. >>> >>> Here's our setup: >>> >>> CentOS 6.4 >>> CouchDB 1.3 >>> SpiderMonkey 1.8.5-7 >>> >>> Replication works fine for over 17,000 documents, then we see this error >>> and can't get past it: >>> >>> [Sat, 11 May 2013 00:55:39 GMT] [error] [<0.12970.4>] Replicator: >>> couldn't write document `bufferhelper`, revision `19-** >>> d339684ee7f5eaf4cc18d84da75383**2d`, to target database `registry`. >>> Error: `unauthorized`, reason: `Please log in before writing to the db`. >>> >>> Any ideas? >>> >>> Thanks, >>> >>> Andy >>> >> -- >> -- >> Job Board: http://jobs.nodejs.org/ >> Posting guidelines: https://github.com/joyent/**node/wiki/Mailing-List-** >> 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 >> nodejs+un...@**googlegroups.com >> >> For more options, visit this group at >> http://groups.google.com/**group/nodejs?hl=en?hl=en<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 nodejs+un...@**googlegroups.com. >> >> For more options, visit >> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >> . >> >> >> >> -- > -- > 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. > > > -- -- 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.
