I would like to deploy multiple django projects that are either completely
unrelated, but deploy them on the same server running apache. I am not a
savvy apache administrator and our small company does not have one. The
use of virtualenv is probably a good idea, but not mandatory in that we
h
I'm not sure you can inherit the whole project, in any case I believe you
could make a boilerplate project and override whatever settings or models
as needed.
On Thu, Feb 14, 2013 at 11:25 AM, Jonathan ATTON
wrote:
> Hello,
>
> I currently have a website made with Django. I use models, databases
On Nov 20, 4:33 am, Stodge wrote:
> I got this working with several sites using Apache. I just created a
> configuration file for each site and pointed it to different settings
> files:
>
>
> SetHandler python-program
> PythonHandler django.core.handlers.modpython
> SetEnv DJANGO_SE
On Thursday 19 Nov 2009 11:01:10 pm Eric Elinow wrote:
> I currently do this for the 5 or so sites that I operate for a client. A
> single Apache setup for Django, with the various virtual hosts being
> directed to their own path(s), and any static media requests being port
> forwarded from ap
i would suggest to everyone start using buildout to develop or deploy.
it gives so many advantages about separation between projects.
a huge advantage is the repetibility of the project and you dont have to
touch the pythonpath of your server, everything is done by the buildout
configuration!
Stod
I got this working with several sites using Apache. I just created a
configuration file for each site and pointed it to different settings
files:
SetHandler python-program
PythonHandler django.core.handlers.modpython
SetEnv DJANGO_SETTINGS_MODULE test.settings
PythonOption django.
On 19 Nov, 2009, at 12:23 , Mark Freeman wrote:
> I currently have a working site running Django and now want to move a
> couple of other of my sites to Django as well. I'm in the process of
> moving off a hosted VPS to my own local server, where the existing
> Django site is.
>
> My questions i
I didn't realise there was a "settings" option for syncdb - it works
beautifully! I now have multi site with multiple databases and one
application installation! Cool...
On Oct 30, 11:29 am, Stodge wrote:
> Oops - this might be what I need:
>
> SetEnv DJANGO_SETTINGS_MODULE mysite.other_settings
Oops - this might be what I need:
SetEnv DJANGO_SETTINGS_MODULE mysite.other_settings
So I created my new settings file that points to a different database
and made a new Apache alias to the new virtual Django site that I want
(so /django/fred instead of just /django). But how do I sync this DB
Sorry, forgot to say that is with mod_python.
On Oct 30, 10:48 am, Stodge wrote:
> Just wondering whether I could write a middleware that parsed
> request.path, say:
>
> /django/site1/index
>
> extracted and removed the site name as "site1" and switched the
> settings on the fly to use settings_
Hi Adam,
> I'm presuming I will use the sites app. However, I don't see how I
> can create and set the SITE_ID through the admin (which is necessary
> for number 2).
>
> Would people suggest that I use the RequestSite class from the sites
> app which uses the HttpRequest variables? If so, does
Russell,
I am working through something similar and I think that the basic
structure would be to have project folders for each site plus a folder
for your shared applications (whose models use the 'Site' object and
'CurrentSiteManager'. Something like this:
/home/django/sharedapps/
/home/django/sh
Hello Russell,
I can't say this is best practice but my approach to a similar goal
has been to create projects for each website. These projects/websites
are unrelated to each other as far as content goes but all install a
common set of apps, some off the shelf, some custom. I have sites
install
On 13 déc, 14:41, barbara shaurette wrote:
> This might be overkill, but you could use middleware and parse for the
> version number in request.path:
>
> from django.conf import settings
> from django.http import HttpResponseRedirect
>
> from mysite import settings as local_settings
>
> class Det
This might be overkill, but you could use middleware and parse for the
version number in request.path:
from django.conf import settings
from django.http import HttpResponseRedirect
from mysite import settings as local_settings
class DetectSiteVersion(object):
def __init__(self):
sel
On 12 déc, 13:14, will0 wrote:
> Hi all
>
> I can't figure out how to change TEMPLATE_DIRS according to the URL
> used.
>
> My purpose is to view two versions of the same site, e.g. mysite/v1/
> and mysite/v2/, but keep the same codebase. This is just for
> development so people in several countr
On 12 déc, 13:33, "Ramdas S" wrote:
> just a suggestion
>
> if it is just the templates you can write a loop inside in settings.py
> based on site_id
>
(snip)
> Pardon me if I didn't understand your question.
Nope. The OP is talking of using different templates for the same site.
--~--~---
just a suggestion
if it is just the templates you can write a loop inside in settings.py
based on site_id
like
if
SITE_ID==1:
TEMPLATE_DIRS =="///
elif SITE_ID==2:
TEMPLATE_DIRS =="somethingelse"
Pardon me if I didn't understand your question.
Ramdas
On Fri, Dec 12, 2008 a
Maybe somekind of offtopic, but trying to run django on cPanel shared
account, got a lot of problems with finalizing crash with error on
splitting an empty request ('host.name','')
Used the same method posted above, any ideas from where is the
problem?
Also additionally the htaccess or direct cal
A dumb question: do you have, in your two dispatch.fcgi files, different values
for DJANGO_SETTINGS_MODULE, or are they the same? And is sys.path different
between the two projects? Because the combination of sys.path and
DJANGO_SETTINGS_MODULE has to be different if you want to load different
Hello,
On Jan 27, 11:45 pm, "James Bennett" <[EMAIL PROTECTED]> wrote:
> A better solution:
Many thanks. I will explore this approach.
Lloyd
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To
A better solution:
1. Completely forget that you ever learned from any source that it
might be a good idea to have a project folder with the apps inside it;
the tutorial does that because it's simpler and easier for purposes of
introducing Django, but in real-world situations it's generally a
ter
Michael Hipp wrote:
> Graham Dumpleton wrote:
>> On Jan 11, 1:13 pm, Michael Hipp <[EMAIL PROTECTED]> wrote:
>>> Graham Dumpleton wrote:
On Jan 11, 8:50 am, Michael Hipp <[EMAIL PROTECTED]> wrote:
> Hello,
> My "main" Django site is working great. But on my shared hosting account
Graham Dumpleton wrote:
> On Jan 11, 1:13 pm, Michael Hipp <[EMAIL PROTECTED]> wrote:
>> Graham Dumpleton wrote:
>>> On Jan 11, 8:50 am, Michael Hipp <[EMAIL PROTECTED]> wrote:
Hello,
My "main" Django site is working great. But on my shared hosting account
(HostMonster) I have multi
On Jan 11, 1:13 pm, Michael Hipp <[EMAIL PROTECTED]> wrote:
> Graham Dumpleton wrote:
> > On Jan 11, 8:50 am, Michael Hipp <[EMAIL PROTECTED]> wrote:
> >> Hello,
>
> >> My "main" Django site is working great. But on my shared hosting account
> >> (HostMonster) I have multiple sites. Some will be D
Graham Dumpleton wrote:
> On Jan 11, 8:50 am, Michael Hipp <[EMAIL PROTECTED]> wrote:
>> Hello,
>>
>> My "main" Django site is working great. But on my shared hosting account
>> (HostMonster) I have multiple sites. Some will be Django, some will be
>> plain html.
>>
>> How do I set this up (specif
On Jan 11, 8:50 am, Michael Hipp <[EMAIL PROTECTED]> wrote:
> Hello,
>
> My "main" Django site is working great. But on my shared hosting account
> (HostMonster) I have multiple sites. Some will be Django, some will be
> plain html.
>
> How do I set this up (specifically in settings.py, urls.py an
it's been a long time since I fooled with an fcgi setup, but as I
recall you can setup htaccess to just work on certain folders rather
than root, which sounds like what you want.
On Jan 10, 3:50 pm, Michael Hipp <[EMAIL PROTECTED]> wrote:
> Hello,
>
> My "main" Django site is working great. But o
Hi Jakub,
There are probably some other answers that will work, but if the only
thing you want to do is allow logins on different servers, possibly the
best solution is for you to either use LDAP/AD or some central
authorization (many others have been interested in this also), or write
your own sy
That's great. So, the views don't, by default, consider SITE_ID then.
Thanks much,
A.
On Sep 7, 2005, at 12:40 PM, [EMAIL PROTECTED] wrote:
Ok, and this means everything will be completely shared. Will the
"site" part of the flatfiles function as I would guess?
Exactly.
Add a site object (has to be done manually in the DB right now) and
then set the site for the flat page.
Ok, and this means everything will be completely shared. Will the
"site" part of the flatfiles function as I would guess?
Thanks!
A.
On 9/6/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Is there support for running multiple sites under a single database?
Yes. Just use the same DATABASE_NAME setting in multiple Django instances.
Adrian
--
Adrian Holovaty
holovaty.com | djangoproject.com | chicagocrime.org
33 matches
Mail list logo
