It's much clear now. Everyone seems to agree the second solution is better.
I've been searching at the same time for the svn, and I've found that
no one does it the same way. But's also true an important number of
the projects are still in pre-magic state.
In the mean time I've also found 'Do's
On 31-Jul-06, at 1:45 AM, Guillermo Fernandez Castellanos wrote:
> Or more like:
> /site1/templates
> /media
> /urls.py
> /site2/templates
> /media
> /urls.p
this makes sense to me, with common stuff somewhere else central
--
regards
kg
Hi,On 7/30/06, Guillermo Fernandez Castellanos <[EMAIL PROTECTED] > wrote:> I'm going to have a server with several domain names serve a few
> applications (blog, photo gallery,...). But I'm a bit at a loss when> dealing with how to organize the different files.I prefer your second
Thanks.
But afterwards, with the second model, how can you integrate it for a
webpage to work?
Imagine a webpage that uses several distinct applications, each one
with different templates, media,... In the webserver you will still
have only one template subdirectory and one media subdirectory.
Guillermo Fernandez Castellanos wrote:
> Hi,
>
of course ,the second model is better,the first one is too much
confused
> I've seen this subject several times in the mailing lists without
> being able to find a definite/useful answer in the mailing list.
>
> I'm going to have a server with
Hi,
I've seen this subject several times in the mailing lists without
being able to find a definite/useful answer in the mailing list.
I'm going to have a server with several domain names serve a few
applications (blog, photo gallery,...). But I'm a bit at a loss when
dealing with how to
6 matches
Mail list logo
