Re: Separate a project into 2 - both need to access the same models

[Merrick]

Got it thanks, I'll try it out.

On Sep 15, 11:47 pm, Daniel Roseman  wrote:
> On Sep 16, 6:45 am, Merrick  wrote:
>
>
>
> > I have a project that I am thinking of breaking up into 2 sites/
> > projects. The goal is to be able to make changes to one site/project
> > without affecting the other one. Here is an example of what each would
> > do:
>
> > mydomain.com
> > -
> > - displays the brochure website (sales copy on the homepage, about,
> > privacy etc...) (Page Model)
> > - tracks visitors as they move around from one Page to another (Access
> > Model)
>
> > dashboard.mydomain.com
> > 
> > - users can login
> > - user can click on a Page and see how many times it was Accessed
> > (Page and Access model)
>
> > So I am operating under the assumption that I will have a total of 2
> > settings files, one for each site/project. I am guessing that I need
> > to define the models Page and Access model on each project. Is this
> > correct? Is there an optimal way of splitting things up to keep up
> > time up, but avoiding repeating model definitions?
>
> > Thanks.
>
> 'Project' is a bit of an artificial concept. The only thing a Django
> site really needs is a settings.py. So you can have two of these, with
> separate Apache vhosts or whatever, but with both referring to the
> same models files - as long as those models are on the Python path.
> --
> DR.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Separate a project into 2 - both need to access the same models

[Daniel Roseman]

On Sep 16, 6:45 am, Merrick  wrote:
> I have a project that I am thinking of breaking up into 2 sites/
> projects. The goal is to be able to make changes to one site/project
> without affecting the other one. Here is an example of what each would
> do:
>
> mydomain.com
> -
> - displays the brochure website (sales copy on the homepage, about,
> privacy etc...) (Page Model)
> - tracks visitors as they move around from one Page to another (Access
> Model)
>
> dashboard.mydomain.com
> 
> - users can login
> - user can click on a Page and see how many times it was Accessed
> (Page and Access model)
>
> So I am operating under the assumption that I will have a total of 2
> settings files, one for each site/project. I am guessing that I need
> to define the models Page and Access model on each project. Is this
> correct? Is there an optimal way of splitting things up to keep up
> time up, but avoiding repeating model definitions?
>
> Thanks.

'Project' is a bit of an artificial concept. The only thing a Django
site really needs is a settings.py. So you can have two of these, with
separate Apache vhosts or whatever, but with both referring to the
same models files - as long as those models are on the Python path.
--
DR.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---