> could change!)? However, at the same time I want to be able to run the
> development environment at http://127.0.0.1/ and want any maintenance
> overhead e.g. managing two sets of url.py files or changing any urls
expanding on Stefan's solution:
You probably want a separate settings.py or at
On Nov 11, 2007 1:44 PM, RichardH <[EMAIL PROTECTED]> wrote:
> From researching posts and blogs, I know this is a difficult issue but
> was wondering whether anyone has come up with simple solutions?
I had a similar problem. My solution was to setup a context processor
which adds a "root" variab
On Sun, 2007-11-11 at 04:44 -0800, RichardH wrote:
> The problem: How do you best configure a Django project so that it can
> be deployed in a production Intranet environment where you don't "own"
> the domain root url, i.e. the Django project appears at
> http://www.mydomain.com/some/url/path/to
The problem: How do you best configure a Django project so that it can
be deployed in a production Intranet environment where you don't "own"
the domain root url, i.e. the Django project appears at
http://www.mydomain.com/some/url/path/to/django/project/name (and it
could change!)? However, at the
4 matches
Mail list logo
