Anyone reading this thread may also want to try
https://github.com/stagas/npm-server

It's a much more minimalistic approach, its only function is to be
able to install packages from a local dir. It will use the real npm
registry to fetch foreign packages and run all other commands (publish
etc). It's more of a development tool than an actual registry but it
may be handy to some.

2013/8/2 pablo borrazas <[email protected]>:
> Hi there,
>
> We have tried to install an npm local registry to improve our development
> workflow taking advantage of this, but we had some issues.
>
> First, we have found that our linux  CentOS 5 server installation was not
> properly because it needs a lot of software updates, and we have to use at
> least CentOs 6.
>
> We still are looking for a good solution to easely switch to our private
> repos or global ones in order to install & publish the modules.
>
> Please, let us now of any update to this issue.
>
>
> On Fri, Aug 2, 2013 at 9:18 AM, Santiago Gimeno <[email protected]>
> wrote:
>>
>> Hi,
>>
>> 2013/8/2 Adam Crabtree <[email protected]>
>>>
>>> I can think of 3:
>>>
>>> 1. Semver.
>>>
>>> Pushing out a critical bug fix can be a liability if every project that
>>> consumes that module, and all its parents must be updated. This is
>>> exacerbated by node.js/npm's default behavior of deeply nested static
>>> dependencies.
>>>
>>> 2. Private Forks of Public Modules
>>>
>>> Ability to publish private versions of public modules. Recently we wanted
>>> a unique fix to forever-agent[1] which request depends upon. You could
>>> achieve this via npm_shrinkwrap (I believe), but that would need to be done
>>> on a per-project basis, whereas being able to publish a private forked
>>> version, while still consuming the public request module is a little more
>>> elegant because now everyone at your company who depends upon request,
>>> doesn't need to remember to include an npm_shrinkwrap.
>>
>>
>> I hadn't thought of these two and now I can see the advantages.
>>
>> Thanks for the thorough response!
>>
>> Cheers,
>>
>> Santi
>>
>> --
>> --
>> 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.
>
>

-- 
-- 
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