Scott Henderson wrote: > Shawn; > > Your answers covered a couple of the thoughts here but I am left wondering > how a depot could be constructed on a generic hosting service.
You can't yet, at this time. If you're speaking of hosting services that only allow static content, that is, or a typical content delivery network setup. > Specifically the main server would be a "normal" depot server and the one > that the world gets its packages would be some type of mirror of this server. We definitely plan to make it so that mirrors can be standard HTTP servers (and possibly ftp, etc.) in the future. However, that isn't possible yet. > I guess what I am getting at is with systems like Debian apt all you need is > a standard http or ftp server to deliver the packages in the end. The packaging systems for these other platforms don't provide a rich set of publishing and metadata operations like we do. Because of that, users have to download an entire set of metadata from their repositories to find out what packages are available. With our approach, a package depot server can efficiently and quickly provide query results to clients without requiring them to download massive data sets. > My last thought here is that maybe you did answer this and a Cherrypy > environment would have to be created on a hosting system. > > If so how? A cherrypy environment just requires that you have the libraries I previously listed installed. There's not much more special to it than that. Cheers, -- Shawn Walker
