search

chadwhitacre / aspen-old-google-code-fork

Automatically exported from code.google.com/p/aspen
0 stars 0 forks source link

think about a packaging format #133

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
think about layering possibilities

how could aspen support easy website composition?

there are site-wide concerns and then there are non-site-wide concerns

database access needn't be site-wide
different parts of a single website could store data in different places 
(though that makes backup/restore more complicated)

- server
- framework
- application

authentication and authorization are sitewide concerns

here's the issue: applications depend on frameworks. So Aspen maybe 
*should* bundle Django and extend it with simplates.

Can be configured for straight WSGI, but OTB bundles an abstraction layer 
over django:

  - defined simplate hierarchy: base.html with certain defined blocks 
exposed and documented; and 
  - applications: module/simplate/config package
  - 

If www roots are scattered about, could they be gathered via symlinks into 
one place for easy url-ish access from the filesystem?

And how is app packaging done in Django currently?

Original issue reported on code.google.com by whit537@gmail.com on 8 Jan 2009 at 3:05