On Fri, Feb 24, 2012 at 11:14 PM, Peter Bittner <[email protected]> wrote: > Luke, > > 2012/2/24 lkcl luke <[email protected]>: >> $ cd pyjamas/doc/pyjs_site >> $ python website.py > > just to clarify: I have not developed/tested with pyjd (i.e. $ python > website.py)
yep - i know :) that's why i ran it: bugs are encountered that are not encountered via pyjs. > I have always _built_ the website ($ pyjsbuild website.py) and tested > with a local vhost pointing to the ./doc/pyjs_site/output folder, thus > mimicing the live website as closely as possible. Some files have to > be copied into or symlinked from within the ./output folder in order > to show as the live website. like any pyjamas application, everything that's in the public/ folder is copied verbatim into the output/ folder and i think that website.py should be absolutely no different in this respect. > (That's the "mess" I had referred to > earlier in another discussion) *sigh* yes, i know. *thinksthinksthinks*... i think it's important to have the doc/pyjs_site be the authoritative place to maintain the files related to the web site. can you put the images into there, even if they're copies? assume that the images on the actual site, whatever location they happen to come from, are *not* as authoritative as what's in pyjs_site/public, and that what's in pyjs_site/public will end up in the output folder and that's what i will end up uploading, thus what's in pyjs_site/public becomes the authoritative location for images etc. l.
