JamesInDenver wrote > What is best practice for configuring repositories? Should one organizing > repos by use in an ALM sense where each repo supports all package types? > Or should there be one repo per package type? > > In our environment, we produce artifacts for .NET, Java, NPM, Bower, etc. > and etc. Do we store all production artifacts in one place or break them > up by type?
Hi James, It is recommended that repositories be broken up by package type, so for example a NPM virtual repository might contain a remote repository pointing to http://registry.npmjs.org/ and your local NPM repository but no different package types. While it may work to combine package types, for purposes of naming and organization, as well as common usage, it makes more sense to keep them broken up unless there is a good reason. -Aaron -- View this message in context: http://forums.jfrog.org/Repo-taxonomy-tp7580153p7580154.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
