My favorites | Sign in
Project Logo
          
New issue | Search
for
| Advanced search | Search tips
Issue 19: Add rawegg: URI scheme for addressing webapp egg files
1 person starred this issue and may be notified of changes. Back to list
Status:  Fixed
Owner:  anrienord
Closed:  Dec 2006
Type-Task
Priority-High
Milestone-0.2


Sign in to add a comment
 
Reported by anrienord, Dec 13, 2006
Python eggs are very nice for deploying web applications (the content &
software modules). Suppose you have prepared some content as standalone
folder with sitemap.xmap and various XMLs inside it. If you package it as
egg and want to deploy it to your production environment, you will need a
way for mounting a sitemap located inside the egg, like this:

<map:pipeline>
  <map:match pattern="api/beta/**">
    <map:mount src="rawegg:mysite_api:/sitemap.xmap" uri-prefix="api/beta"/>
  </map:match>
</map:pipeline>

"Raw" means here that you access file content by directly reading files
stored on file system, not by retrieving data from sitemap pipe inside egg
by URI. egg: URI is much like block: URI in Apache Cocoon
<http://wiki.apache.org/cocoon/BlocksDefinition>, but differs in
deployment. An example of egg: URI could look like this:

<map:generate src="egg:mysite_api:/news/{request-param:id}"/>

Comment 1 by anrienord, Dec 13, 2006
If you distribute your webapp as Python egg, all you need to run your site is:

$ pycoon --serve cherrypy localhost 8080 rawegg:mysite:/pycoon.xconf

Status: Fixed
Comment 2 by anrienord, Feb 26, 2007
(No comment was entered for this change.)
Labels: -Milestone-pysitemap-0.2 Milestone-0.2
Sign in to add a comment

Hosted by Google Code