No, what I mean is more like this. You have one set of urls that act
like a master. Each url should be
similar to
('something/$', 'view-handler')
Notice that it doesn't use ^, so it will match anywhere. Then, on your
seperate sites, you have a site
specific url config that includes this
Wouldn't that just be the same thing, except 4 copies of them exist in
appurls.py instead of urls.py?
My urls.py is in my source control tree, because there are so many of
them, we each pull it down. I know we could take it out of source
control and hand change it each time to have /dev1 or
Yea, there is a way. If you take all your url out, and move them into an
appurls.py file or something,
you can include this from the main urlpatterns. E.g:
urlpatterns = ('', ('^yourprefixhere/',
include('pythonpathtoproject.appurls'))
I think that should work - there might be other ways
I tried doing that, even though it seemed messy..and it complained
about having more than 255 arguments ?
On Apr 20, 10:49 am, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
> Ok...that fixed that problem...
>
> Is there any better way to handle the urls.py file though...than
> putting different
Ok...that fixed that problem...
Is there any better way to handle the urls.py file though...than
putting different versions of each url? I currently have about 100
urls...and I'm going to have to put 4 versions in for each..seems like
there should be an easer way to append something to the
You need to set PythonInterpreter directive in each Location container
directive with a different value in each case. This is so that each
Django instance runs in its own Python sub interpreter. You should
also change your settings.py file for each and set SESSION_COOKIE_NAME
to a different value
Also...it seems if I have two instances of this running on the same
apache server...that one sporadically looks at the wrong urls.py file
( the one for another instance )
Is it not valid to do the following in the apache conf file?
SetHandler python-program
PythonHandler
I don't think I can convince our network guys to do that... they
prefer not to open anymore ports than necessary.
On Apr 20, 12:28 am, "Julio Nobrega" <[EMAIL PROTECTED]> wrote:
> You could use different directories (Django projects) under multiple
> VirtualServers (different domain names /
You could use different directories (Django projects) under multiple
VirtualServers (different domain names / ports), each one for a
particular developer.
On 4/20/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> I'm trying to setup three development directories for different
> programmers,
I'm trying to setup three development directories for different
programmers, for us each to be able to checkout our project to from
svn on the same development machine...
Basically, I wanted to setup apache to have
/projectname = main merged project instance
/dev1/projectname = developer #1
10 matches
Mail list logo
