Re: [Spyce-users] Suggested spyce project organization

[Jonathan E. <jon...@si...>]

Jonathan Taylor wrote:
> Hi,
> 
> I am trying to figure out how ppl usually organize a spyce project with 
> .spy, .spi and .py files.  I have been getting by for the last 6 months 
> with various amounts of hackery.
> 
> I have something like this so far:
> 
> project
> - wwwroot
> - src
> - lib
> 
> I was thinking of putting spy in wwwroot, spi in src, and py in lib and 
> then soft link project/wwwroot to a web accessible dir such as 
> ~/public_html/project.
> 
> I seem to be able to access the .spi by:
> 
> [[.include file="../src/output_fns.spi"]]
> [[.include file="../config.spi"]]
> 
> And I am trying to get config.spi to somehow add the absolute path of 
> lib to sys.path so that I can access these .py modules in any .spy file 
> in the wwwroot.  This seems easier said then done.  I think I can get 
> the path by os.path.realpath(request.path()) and stripping off the end.

With spyce 2, all you would do is
sys.path.append(os.path.join(root, 'lib'))

after you define root in spyceconf.py.

> I'd be interested in hearing any suggestions for doing what I am doing. 
>  More importantly, am I making this harder than it is?  

wrt request.path, yes :)

> Is there some 
> simple organization I am not thinking of?  All in one dir seems like a 
> good idea to me but then ppl can download my .py and .spi files possibly 
> getting db passwords etc.  Bah.. ;)

Well, it depends how big your app gets -- all in one dir starts to get messy 
past a couple dozen files.  SilentWhistle is organized pretty much the way you 
describe.

(If you wanted to go the simple route, you could use mod_access to keep people 
out of your .spi and .py files.)

> P.S. Kudos to Jonathan Ellis for the great work recently.

Thanks!

-Jonathan