StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO"sites framework" on a single django instance
primarykey
Id
1007017
data
AcceptedAnswerId
1008410
AnswerCount
2
ClosedDate
CommentCount
5
CommunityOwnedDate
CreationDate
2009-06-17T13:27:59.197
FavoriteCount
10
LastActivityDate
2011-03-28T15:45:53.593
LastEditDate
2011-03-28T15:45:53.593
LastEditorUserId
2908
OwnerUserId
2908
ParentId
0
PostTypeId
1
Score
6
ViewCount
3733
LastEditorDisplayName
text
Body
I want to serve up specialized RSS feeds on a different subdomain from the rest of the site. Can I use the sites framework to use a different urls.py and settings.py file within a single django instance. or do I need to set up two apache locations and just set the different settings.py files in the apache conf. The reason I need to set up two urls.py files is to avoid duplicate content. I don't want the main site to be available at rss.example.com and I don't want the specialized feeds to be accessible on example.com Serving them from a single django instance would be ideal because we're on shared hosting with limited memory, and it seems like such a waste to have an instance open that only serves up rss. edit: I concluded that multiple instances with seperate urls.py files would be easiest for me... but I found this article describing how to do it using a single instance: <a href="http://effbot.org/zone/django-multihost.htm" rel="noreferrer">http://effbot.org/zone/django-multihost.htm</a> <h1>Solution: <a href="https://bitbucket.org/jiaaro/django-tupperware/src/" rel="noreferrer">Django tupperware</a></h1> I ended up writing a framework for running multiple copies of a site on a single django instance. The basic idea is to change out the <code>SITE_ID</code> setting on the fly for each request and load alternate settings from the database. It does this based on domain and uses <code>SITE_ID = 1</code> by default (when it can't find anything) All settings in the settings.py file act as defaults which are overridden by the settings stored in the database for the current site. It works pretty well :) and it's running in production at <a href="http://rootbuzz.com" rel="noreferrer">http://rootbuzz.com</a>
Tags
<django><apache><rss><settings><sites>
Title
"sites framework" on a single django instance
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USJiaaro
UserOwnerUserId
1. USJiaaro
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
2. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.