This example shows the basic configuration for a non-load-balanced depot server. This example connects http://pkg.example.com/myrepo to internal.example.com:10000.
See Serving Multiple Repositories Using Web Server Access for instructions about setting other properties you need that are not described in this example.
Configure the depot server with a pkg/proxy_base setting that names the URL where the depot server can be accessed. Use the following commands to set the pkg/proxy_base:
$ svccfg -s pkg/server add repo $ svccfg -s pkg/server:repo setprop pkg/proxy_base = astring: http://pkg.example.com/myrepo $ svcadm refresh pkg/server:repo $ svcadm enable pkg/server:repo
The pkg(5) client opens 20 parallel connections to the depot server when performing network operations. Make sure the number of depot threads matches the expected connections to the server at any given time. Use the following commands to set the number of threads per depot:
$ svccfg -s pkg/server:repo setprop pkg/threads = 200 $ svcadm refresh pkg/server:repo $ svcadm restart pkg/server:repo
Use nocanon to suppress canonicalization of URLs. This setting is important in order for search to work well. Also, limit the number of back-end connections to the number of threads the depot server provides. The following partial httpd.conf file shows how to proxy one depot server:
Redirect /myrepo http://pkg.example.com/myrepo/ ProxyPass /myrepo/ http://internal.example.com:10000/ nocanon max=200
For information about the Oracle Solaris SSL kernel proxy and using SSL to encrypt and accelerate web server communications, see Chapter 3, Web Servers and the Secure Sockets Layer Protocol, in Securing the Network in Oracle Solaris 11.2 .