Shankar,
Here my structure (some ideas from pinax and some from / based on Bruce's
approach ;-). As I'm using eclipse I have automatically a src directory,
which isn't necessary, but it also doesn't hurt.
Basic idea is that I prefer to have important parts used under manual
control. It's not really elegant, but stable and (should) prevent confusion.
This paproach is usable for any django project, not only satchmo projects.
/opt/
_framework/django/
/original_SVN/django
/1.0/django
_framework/django-apps/
satchmo
/original_SVN/satchmo
/freeze_rev_NUMBER/satchmo
django-wiki
django-multilingual
...
_framework/python-libs/
trml2pdf
pil
...
deve/workplace/project/
fixtures/
external_apps/
libs/
bin/
src/
__init__.py
local_settings.py
manage.py
settings.py
apps/
static/
templates/
1) in /original_SVN/satchmo you have always the runk from SVN
2) once you are happy with it and wnat to productionize you copy it ov er
with that state into freeze_rev_NUMBER. Numer is the SVN version when you
copied - this heps you to track.
3) in external_apps you symlink (use junction on win32 ntfs systems)
to /original_SVN/satchmo (or a froozen one, if you are stable)
to /original_SVN/django (or a froozen one)
to any additional django apps you want to use
NOTE: Symlink always into the directory where the application is
located
4) in external_libs you symlink with the libraries (you don't need, I just
prefer it this way for some libs)
5) I use a modified manage.py (from pinax) to set the python path
accordingly.
--------------- snipe -----------------
path = addsitedir(join(settings.FRAMEWORK_ROOT, "external_apps""), set())
if path:
sys.path = list(path) + sys.path
sys.path.insert(0, join(settings.FRAMEWORK_ROOT, "libs"))
sys.path.insert(0, join(settings.PROJECT_ROOT, "apps"))
if __name__ == "__main__":
execute_from_command_line()
6) in deve/workplace/project/ you keep all data you are working on in the
actual project, in project/src you code/html.
7) in src/apps you write your own apps if there are) for the project/store
8) in src/templates you write your own templates for the project/store. To
ensure that it first looks in your directory you must set
TEMPLATE_DIRS in the correct order. Yours first, then the ones it should
fallback.
Maybe this gives you some ideas how to struct your projects
g
-----Ursprüngliche Nachricht-----
Von: [email protected] [mailto:[email protected]]
Im Auftrag von Shankar Dhanasekaran
Gesendet: Freitag, 09. Jänner 2009 23:09
An: [email protected]
Betreff: Re: template changes not showing
Hi Dan,
I appreciate your help. If you dont mind, please can you help me INSTALLING
THE LATEST SATCHMO? I have earlier started a project as per bruce's plan and
i can follow the same now. I have no problem with that. My main problem now
is to install satchmo in its latest svn version.
Should I link each and every folder in /app folder to
/usr/lib/python2.5/site-packages/ by 'ln -s' individually?
The official setup.py instruction doesnt work and nowhere can i find any
information on INSTALLING SATCHMO.
Thank you so much Dan,
Shakthi
----- Original Message -----
From: "Dan Harris" <[email protected]>
To: "Satchmo users" <[email protected]>
Sent: Saturday, January 10, 2009 3:30:30 AM GMT +05:30 Chennai, Kolkata,
Mumbai, New Delhi
Subject: Re: template changes not showing
Have a look at Bruces tutorial at:
http://gosatchmo.com/starting-a-new-store-real-world-project-layout
I set up my projects roughly like that and then overriding templates is as
easy as making ones with the same name the appropriate templates
subdirectory.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Satchmo users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/satchmo-users?hl=en
-~----------~----~----~----~------~----~------~--~---
