speeran wrote > Jeremy > > Any status on our problem? > > Thanks > > Syed > > From: Syed Peeran [mailto:
> speeran@ > ] > Sent: Sunday, April 03, 2016 12:28 AM > To: > [email protected] > ; > jeremy@ > Subject: Re: [Artifactory-users] [#38510] Registering/deploying a private > Bower package? > > Jeremy > > Please review the logs and get back to me > As we need to solve the problem > > Thanks > > Syed > 909-816-6708 (cell) > > > From: Syed Peeran > Sent: Wednesday, March 30, 2016 5:54 PM > To: > [email protected] > <mailto: > [email protected] > >; > jeremy@ > <mailto: > jeremy@ > > > Subject: RE: [Artifactory-users] [#38510] Registering/deploying a private > Bower package? > > I have attached the artifactory log per request > > Please get back to me with a solution > > Thanks > > Syed > From: JFrog Support [mailto: > support@ > ] > Sent: Wednesday, March 30, 2016 1:12 AM > To: > jeremy@ > <mailto: > jeremy@ > > > Cc: > [email protected] > <mailto: > [email protected] > > > Subject: Re: [Artifactory-users] [#38510] Registering/deploying a private > Bower package? > > Hi Jeremy > > We have received an information that you have raised a question on the > Artifactory Forums. We suggest that the next time you will raise your > issues directly to JFrog Support by sending email to > support@ > <mailto: > support@ > >. > > Regarding the issue that you have raised, the bower register command > requires the package name and also pointing to a URL of the package when > it's stored. When you are using the local repository that configured to > support Bower, then you need to deploy the package as tar.gz file into > this repository manually. Upon deploying the package, you don’t need to > register this package since upon pointing to Artifactory, the artifact > will be found and delivered to the client by using the bower.name and > bower.version that are extracted from the bower.json file. The bower > register command works upon remote/virtual repositories since this command > requires to have the package name and the URL that pointing to the package > that is stored on your VCS. Upon doing so, the information is added as > properties to the remote repository and when the registry field in the > .bowerrc file is pointing to Artifactory, the client can retrieve the > artifacts from the remote repository after registering the private > packages. You can find more information > here<https://www.jfrog.com/confluence/display/RTF/Bower+Repositories>. > > Hope this helps, > Best Regards, > Alex > JFrog Support > > > > [http://storage.pardot.com/27942/156192/getfastersupport_HiRes.jpg] > On Tue, 29 Mar at 9:56 PM , artifactory-users < > [email protected] > <mailto: > [email protected] > >> wrote: > jeremy.tice wrote >> I love that Artifactory supports Bower, but I'm running into some >> roadblocks when I try to use it for non-public packages. I have local, >> remote, and virtual repos set up (with the virtual one combining the >> other >> two), and I've gotten it installing dependencies through the virtual repo >> successfully. However, I can't seem to figure out how I'm supposed to be >> deploying/registering my own packages. When I try to use the > >> command, I get, depending on the repo I try to register with... >> >> virtual: > >> remote: > >> local: > >> >> So... I get the sense that I'm approaching this wrong, and would >> appreciate any help! > > An update in case anyone else was struggling with this. I eventually got > it > to work by ignoring the "register" command, and deploying directly to the > local bower repo in Artifactory, with this shell script. > > > > I still get the sense that there /should/ be some cleaner, more automatic > way to do this, but "bower install mypackage" works now (with the registry > pointed at that same virtual bower repo), so I'm happy. > > > > -- > View this message in context: > http://forums.jfrog.org/Registering-deploying-a-private-Bower-package-tp7580867p7580868.html > Sent from the Artifactory - Users mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Transform Data into Opportunity. > Accelerate data analysis in your applications with > Intel Data Analytics Acceleration Library. > Click to learn more. > http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140 > _______________________________________________ > Artifactory-users mailing list > [email protected] > <mailto: > [email protected] > > > https://lists.sourceforge.net/lists/listinfo/artifactory-users > 38510 > > ------------------------------------------------------------------------------ > > _______________________________________________ > Artifactory-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/artifactory-users Yes, you can mark this resolved. I figured out the process for deploying the private package to the local repository manually the day after my initial question. -- View this message in context: http://forums.jfrog.org/Registering-deploying-a-private-Bower-package-tp7580867p7580885.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
