[added CC pkg-discuss] Steve Goldberg wrote: > Hello, I am learning about IPS and would like a deeper understanding of the > Package Depot Server Mirror. I would like to place my mirror depot servers > at various service providers facilities (essentially unmanaged). I would like > a deeper understanding of the software components that are required on the > package depot server mirror. Thus far I understand that SFM is leveraged and > IPS packages. What I'd like a better picture of is what constitutes the > mirror server. Is it merely a web server? Is it a web and app server? What > does the software stack and dependencies between tiers in the stack look like?
The IPS depot server is still under heavy development, so what is describe here is subject to change. The depot server is a cherrypy-based [1] web application that is intended serve repository package content, package metadata, and allow publishing operations. It is not intended to be used as a general purpose web server, although it can serve dynamic and static content. To facilitate the customisation of the depot server pages, the --content-root parameter allows you to specify a location to serve static and dynamic web content from. The depot server can operate in three modes: * normal (can serve package content and metadata, and allows publishing operations) * readonly (can serve package content and metadata, but does *not* allow publishing operations) * mirror (can serve package content, but *not* metadata, and does *not* allow publishing operations) These are the software requirements for the current version in the pkg gate tip: * python 2.4 * pyOpenSSL 0.8 * cherrypy 3.1.0+ (but less than 3.2.0) * python ply 3.0 [2] Please let me know if this isn't enough. Cheers, -- Shawn Walker [1] http://www.cherrypy.org [2] http://www.dabeaz.com/ply
