I have a similar situation, in that I have been implementing a website
for my company which is trying to move data from excel spreadsheets
into a web app that manages the "stuff" we track. agree with Kevin
that I think you want one project (I'm assuming by project you mean
settings.py file), and that project contains multiple apps. In my
situation I have a chipmanager app, a taskmanager app, and a
forummanager app. I am in a big company, let's say it's called
foocorp, and the name of my webapp is called "myapp". I have urls
like this:
myapp.foocorp.com/chipmanager/chip/add
myapp.foocorp.com/chipmanager/chip/edit/<chipName>
myapp.foocorp.com/taskmanager/tasks
myapp.foocorp.com/taskmanager/tasks/<taskId>/edit
myapp.foocorp.com/forummanger/topic/<topicId>
myapp.foocorp.com/forummanager/edit_post/<postId>
The various apps all talk to each other, but each has its own
urls.py. For example, the taskmanager pages for tasks have a button
button in the task display to go to a forum for the task. This takes
you to a page that is in the forummanager. I use the {% url %}
template command heavily in my html, and this has also proven to be
very flexible, compared to html that has hardcoded html paths in it,
or even relative ones. I worked with someone else's app that used
just html links in their templates, and moving that app into my
environment was a lot of unnecessary pain that could have been avoided
had they used {% url %} in their templates in place of links that
contained '..' and '/'. Hope this makes sense. If not, start
exploring and it will ...
I will say that in the beginning, what was in what app was muddled in
my head. To get going I used just a single urls.py file and basically
had a single app. But over time it became more clear how to make it
more modular and I refactored into the multiple apps. This has proven
to be much more maintainable and understandable, so I definitely
recommend it.
We have just recently moved onto having a domain and using apache.
IE, this allowed me to serve the website from myapp.foocorp.com. I
had some help on the apache/it side, so I can't give you a ton of
details, but basically we requested a dns alias 'myapp.foocorp.com'
from my company's IT group and then created an apache configuration
file that allows me to serve up my app from myapp.foocorp.com. We
used fcgi.
I believe that if I had some other app that I wanted to serve through
maypp.foocorp.com/wiki, that that could be done using some apache
magic that picks out the /wiki and then sends that to your wiki app.
Hope this helps!
Margie
On Apr 30, 10:58 am, "eric.frederich" <eric.freder...@gmail.com>
wrote:
> Kevin,
>
> Yes...that is what I was thinking but I wasn't sure if it was the
> "correct" thing to do. You saying that helps ease my mind.
>
> Also, one concern I had was that if I did this and the "1 project to
> rule them all" was hogging up the root directory "/", would I still be
> able to have other non-django apps on this server? Would I be able to
> havehttp://someserver/wiki/and have it go to a MediaWiki or would it
> be going through my django app and matching my urlconf?
>
> Sorry...I know even less about Apache than I do django, python, or web
> stuff in general.
>
> Thanks,
> ~Eric
>
> On Apr 30, 1:42 pm, Kevin Audleman <kevin.audle...@gmail.com> wrote:
>
> > Your needs are a bit vague, but here's a thought:
>
> > I would think that you would want one project which would conceptually
> > encompass everything your company does. Within that project you would
> > create multiple apps: one for training and one for project XYZ (if I'm
> > reading your requirements correctly). This way the logic for each
> > "project" would be contained in its own directory complete with views,
> > models, etc. They will live in the same Django project and share a
> > settings.py file, urls.py file and can easily talk to each other.
>
> > Kevin
>
> > On Apr 30, 7:47 am, "eric.frederich" <eric.freder...@gmail.com> wrote:
>
> > > So, I have been tasked with creating a new website within my company
> > > for a new project. Lets call the project XYZ (because just calling it
> > > 'the project' is confusing since Django already has a concept of
> > > projects).
>
> > > The website will be your run of the mill project page with
> > > announcements, newsletters, presentations etc.
> > > One other thing they wanted was to be able to manage and track
> > > training for XYZ.
>
> > > We have been looking to change the way we track other training
> > > (currently in a spreadsheet) for a while now. I took the opportunity
> > > and created a Django application for all training, not just for XYZ.
> > > I'd like it to live athttp://someserver/training/. From there they
> > > could find training on AutoCad, Visio, MathCad, as well as XYZ.
>
> > > For the XYZ project page, I'd like it to live athttp://someserver/XYZ/.
>
> > > So now here's the question. Should the training site and the XYZ site
> > > both be projects? If they're both projects, how could I get a list of
> > > all XYZ training courses from the XYZ project page? That would
> > > involve 1 project pulling data from the other.
>
> > > I could just have one Django project at '/' instead of one at '/
> > > training' and one at '/XYZ'. Doing that, getting a list of XYZ
> > > training courses up on the XYZ project page would be easy. Now is
> > > having a single Django project hogging up '/' going to prevent me from
> > > running other things like a MediaWiki or BugZilla? Do I need to use
> > > "http://someserver/django/training"; and "http://someserver/django/
> > > XYZ"?
>
> > > So I need some help deciding what to do. Multiple projects or a
> > > single project? If I do multiple, how can I access models across
> > > projects. If I do a single project how do I configure Apache in a way
> > > that won't mess things up down the road?
>
> > > What would you do?
>
> > > Thanks in advance.
> > > ~Eric
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
