Configuring the http/https proxies

131 views
Skip to first unread message

niristotle okram

unread,
Dec 2, 2015, 2:55:22 PM12/2/15
to nexus...@glists.sonatype.com
I am testing a cookbook with chef that sets up the Sonatype nexus server. Apparently the proxy repositories (the default ones) will not fetch/proxy until i configure the http/https proxyies from the nexus's UI (via the administration - Servers). Can anyone tell me where is this store, so that i configure on the file rather than leave a manual step for anyone to punch in manually. 
The server itself have the proxy configured in the ENV  


Regards, 

Rich Seddon

unread,
Dec 2, 2015, 3:17:26 PM12/2/15
to niristotle okram, nexus...@glists.sonatype.com
Apparently the proxy repositories (the default ones) will not fetch/proxy until i configure the http/https proxies from the nexus's UI (via the administration - Servers). 

I'm not sure what you mean by this, can you clarify? 

Rich

--
You received this message because you are subscribed to the Google Groups "Nexus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nexus-users...@glists.sonatype.com.
To post to this group, send email to nexus...@glists.sonatype.com.
To view this discussion on the web visit https://groups.google.com/a/glists.sonatype.com/d/msgid/nexus-users/CAPzcO4gCGQBVg_-Q3DO82xaJxtUFXc_9WPHPcHmH1FzQHhx%2BEw%40mail.gmail.com.
For more options, visit https://groups.google.com/a/glists.sonatype.com/d/optout.

niristotle okram

unread,
Dec 2, 2015, 4:33:57 PM12/2/15
to Rich Seddon, nexus...@glists.sonatype.com
Sure, once i complete the test to build the sonatype nexus server. I log-in but when i click on the 'Central' proxy repo then click on the "browse remote" on the new install. There folder were not available. But after configuring the proxy (pic: nexus-proxy.png), they showed up (pic central-repo.png). 
--
Regards
nirish okram
central-repo.png
nexus-proxy.png

Rich Seddon

unread,
Dec 2, 2015, 5:36:07 PM12/2/15
to niristotle okram, nexus...@glists.sonatype.com
This information is stored in the nexus configuration files under sonatype-work/nexus/conf.   Directly manipulating these files isn't supported, we make no guarantees that the format will stay the same between releases.   But we do support upgrading configuration files from older versions, if old versions of these files are found in the conf directory they'll be upgraded automatically at startup.   

So what you can do is set up things like this in a test instance, and then have chef put the resulting configuration files into the sonatype-work/nexus/conf directory when it sets up a new instance.

Alternatively you can use the REST API to populate these settings:

Fraser

unread,
Dec 3, 2015, 2:36:24 AM12/3/15
to Nexus Users
I would certainly recommend using the RESTful API, that's what we use for managing many Sonatype-Nexus resources (currently on v2.11.x) including config settings such as proxies (in fact we use Puppet modules which abstract this further so it is straight-forward to create new (immutable) instances of Nexus servers as well as subsequent creation and management of user defined repos, groups, etc..). All-in-all very much easier than messing around with files which sometimes require a restart of the service to be noticed.

Rich, on the subject of the HTTP/REST API for Nexus v3.x. As yet there are no published details that I can find, and this is making it very difficult for me to plan our migration to v3. Is there *anything* that you can point me to that describes what services and resources are available so I can begin this work. I don't mind if it's still in alpha/beta whatever, it's just so central to the way that we provision Nexus in our Cloud that its current a blocker to even guesstimating what the effort will be to transition, and in reality I much prefer to get some 'hands on' now. Some of my colleagues are asking me to 'stand up' a version 3 'sandbox' instance so that they can begin looking at some of the Docker support and such like. I'd really like to NOT build these by hand while waiting for the published API since that is firmly against the principles that we follow for automation. It would be great to 'kill two birds with one stone' as it were.

Very happy to work with Sonatype and this forum in testing and providing feedback for what you have now on the HTTP/REST API and as this progresses through whatever milestone releases remain before GA.

Anything you help me out with her ?

Kind Regards

Fraser.

Reply all
Reply to author
Forward
0 new messages