Local and Remote Repositories

Oct 7, 2010 at 12:38 PM

I'm sure our company isn't the only one to have libraries and packages internally used and available for internal development.   Would it be possible to be setup with multiple repositories and set a priority to each?  Or simply in order of precedence?

I think I'm thinking more along the lines of say:

1.  Local Corporate Repository

2.  Public External Repository

Adding a package will check the Local first, because it's first in the list, if it doesn't find it, it'll move on to the Public one and do the same.   That way if there is a package in both locations, because perhaps we have a modified version for our needs available, it'll take that one rather than the public one first.   Not to mention, it would provide us with a better way to make the internal packages available to our developers that stays consistent with their new way of retrieving packages in general. 

I could see this as useful in many open source projects as well.  Making packages available for the team, that the general public doesn't necessarily care about.

Oct 7, 2010 at 5:20 PM

Currently, you can set up a private repository by simply putting a set of packages in a network share and then simply add the UNC path to NuPack. Currently, we don't have fallback behavior, but we already have a bug for it.

Check out this video for an example: http://channel9.msdn.com/Shows/Web+Camps+TV/Web-Camps-TV-8-NuPack-with-Phil-Haack

Oct 7, 2010 at 10:55 PM
This is a great idea. I believe there is an open issue for the feed searching and priority - I know there is a couple of discussions already about this. 
"Be passionate in all you do"