Thank you all for the replies.
I will try the middleware solution and tell you how it's going. :)
It's nice to see that our group is big enough to get ~15 replies in 2
days.
Thanks,
Arshavski Alexander.
On Feb 5, 5:14 am, Graham Dumpleton
wrote:
> On Feb 5, 1:25 am, Adam Stein wrote:
>
> > I
On Feb 5, 1:25 am, Adam Stein wrote:
> I do something similiar where I have an extra item in the url. To get
> Apache and the Django server to match, I just add the extra part in
> urls.py that I'm matching. So instead of something like:
>
> (r'^admin/(.*)', admin.site.root)
>
> in Alex's cas
Ah yes, not being able to change urls.py would make it more difficult.
Somebody is making your job way too hard :-{}
On Wed, 2009-02-04 at 15:29 +0100, Ales Zoulek wrote:
> > That way, the exact same URL can be used in both places.
> Yep. But the urls.py cannot :)
>
> That was why I suggested th
> That way, the exact same URL can be used in both places.
Yep. But the urls.py cannot :)
That was why I suggested the solution with midlleware. Which is
conditionaly loaded
Example:
settings.py:
if DEBUG:
MIDDLEWARE_CLASSES = ['project.mw.InjectUrlPrefix'] + MIDDLEWARE_CLASSES
>
> On W
On Wed, Feb 4, 2009 at 9:11 AM, Ales Zoulek wrote:
>
> As I undrestood it is that it's infact *used* on Apache.
> That's why the django project is on "/peergw" - Apache, but "/" - dev
> server.
>
>
That the "/peergw/" is needed to reach the code running on Apache implies
the Location block for th
I do something similiar where I have an extra item in the url. To get
Apache and the Django server to match, I just add the extra part in
urls.py that I'm matching. So instead of something like:
(r'^admin/(.*)', admin.site.root)
in Alex's case, it would be:
(r'^peergw/admin/(.*)', admin.site.
As I undrestood it is that it's infact *used* on Apache.
That's why the django project is on "/peergw" - Apache, but "/" - dev server.
And Alex wants to simulate this behaviour on dev server side.
Or am I wrong?
A.
On Wed, Feb 4, 2009 at 3:02 PM, Karen Tracey wrote:
> On Wed, Feb 4, 2009 at
On Wed, Feb 4, 2009 at 4:46 AM, Ales Zoulek wrote:
>
> That's not as easy as it seams, quick fix/hack would be middleware
> that strips out /pergw from the url. That middleware would be used
> only for dev server, not for apache.
>
>
What about simply using the django.root PythonOption when runni
That's not as easy as it seams, quick fix/hack would be middleware
that strips out /pergw from the url. That middleware would be used
only for dev server, not for apache.
A.
On Wed, Feb 4, 2009 at 9:39 AM, knight wrote:
>
> My production version is running on different computer with apache
>
My production version is running on different computer with apache
installed on http:///peergw
and development version on my computer is running on http://.
I want them both to run on http:///peergw.
The port has no difference.
Thanks, Alex A.
On Feb 4, 9:58 am, Ian Lewis wrote:
> What are you
What are you trying to do? If your development appserver is conflicting with
a locally installed apache then why not just use a different port?
python manage.py runserver 8001
2009/2/4 knight
>
> Hi,
>
> My question is:
>
> Is there a way to change my default app url in development server
> fro
Hi,
My question is:
Is there a way to change my default app url in development server
from http://localhost:8000 to http://localhost:8000/peergw.
If it's a problem, maybe someone have a good reference for configuring
apache server on MAC.
Regards,
Arshavski Alexander.
--~--~-~--~~-
12 matches
Mail list logo
