I'm trying to get my mind round django. I have it installed on my
unbuntu server, it works, I've worked through tutorials 1 and 2 and a
bit of 3. I can get the admin screens up and the basics of the polls
example work.
However two rather basic things still elude me:-
Where/how do I actually start creating the top level/page of a web
site? Do I just open vi and create some HTML and embed django
code? That seems unlikely but I can't see anywhere that tells me
what the code that creates a django site looks like and/or where it
resides. An actual example of a two or three page working django
based web site would be a huge help.
I can't see anywhere that seems to tell me the issues involved with
moving from using the built in web server to using apache2 (or
whatever, I have apache2 on my system).
I know that in a few days time when I have got over the initial hump all
the above will seem trivial so sorry to ask, but at the moment I'm
feeling a bit lost! :-)
--
Chris Green
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django...@googlegroups.com.
To unsubscribe from this group, send email to django-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
just finish the tutorial. seriously, even if you're so experienced,
it's a much needed introduction.
about how to write, check the paragraph about the MTV architecture:
model, view template. in short, that means: write your models with
most of the conceptual functionality; then write a view that gathers
all needed info from the models and calls a template to show it as a
web page. templates should have very minimal 'code' embedded, just to
display the data gathered by the view.
but please, do the tutorial.
--
Javier
sorry, but no.
a Django view is way different from an MVC view, there's nothing like
controller in django (fortunately, that's a GUI concept, not a web
thing; and no, urls.py is not a controller), MVC doesn't separate view
from template like Django does, and lots more....
--
Javier
I've seen a few different patterns in regards to this question. One scenario is where you have a multi-purpose Django site comprised of multiple reusable apps with no obvious top-level entry point, you can create a view "def index(request)", and have it render a template with whatever data you want to send it -- including perhaps no data at all. Then map your index view to '/' in urls.py at the project level, put together a template and you're all set.
Another option I've seen is if you have a single-purpose site where one app is primary, you map your primary app's start page as your index. An example would be a blog, and you would set up your chronological entries list page as the index.
>
> I can't see anywhere that seems to tell me the issues involved with
> moving from using the built in web server to using apache2 (or
> whatever, I have apache2 on my system).
The short version is that the built-in server was built as a just-good-enough-to-use-while-developing solution, and is not sufficient to handle more than a minimal load. The trade-off is that configuring apache2 + mod_wsgi, or nginx + gunicorn, is more complex than just running the devserver.
Hope this helps a bit,
---Peter Herndon
No/yes, I *do* have Python experience, it's my language of choice for
scripts which require a bit more than basic shell scripting.
> Also - have you read the intro overview, as that pretty much answers your
> questions, unless I'm missing something
> [1]https://docs.djangoproject.com/en/1.3/intro/overview/
> Cal
>
I've looked at that, but maybe not hard enough. A quick glance seems to
raise some of the same questions, there are lots of code snippets in
there but it's not *very* clear where they all live or even whether one
has to write them or they're generated by django. It does seem a bit
clearer at a second reading though so I suspect it will all become clear
eventually.
--
Chris Green
--
Chris Green
--
Chris Green
>
> >
> > I can't see anywhere that seems to tell me the issues involved with
> > moving from using the built in web server to using apache2 (or
> > whatever, I have apache2 on my system).
>
> The short version is that the built-in server was built as a just-good-enough-to-use-while-developing solution, and is not sufficient to handle more than a minimal load. The trade-off is that configuring apache2 + mod_wsgi, or nginx + gunicorn, is more complex than just running the devserver.
>
Sorry, I maybe didn't explain well what I wanted. I realise that
configuring apache2 to do all this involves more work, what I wanted was
the steps required to go from a working django project under the
built-in server to one that works under apache2.
Someone else has pointed me at https://docs.djangoproject.com/en/1.3/howto/deployment/modwsgi/
though which seems to be what I need.
--
Chris Green
this is as simple as it gets
https://bitbucket.org/lawgon/django-addition/overview
--
regards
Kenneth Gonsalves
On Wednesday, 5 October 2011 20:55:33 UTC+1, Chris Green wrote:
I'm an experienced programmer (started around 1971 or so!) and I've done
lots of things over the years, much of my background is in Unix (Solaris).
In the last few years I have done quite a lot of web related stuff.I'm trying to get my mind round django. I have it installed on my
unbuntu server, it works, I've worked through tutorials 1 and 2 and a
bit of 3. I can get the admin screens up and the basics of the polls
example work.However two rather basic things still elude me:-
Where/how do I actually start creating the top level/page of a web
site? Do I just open vi and create some HTML and embed django
code? That seems unlikely but I can't see anywhere that tells me
what the code that creates a django site looks like and/or where it
resides. An actual example of a two or three page working django
based web site would be a huge help.
I can't see anywhere that seems to tell me the issues involved with
moving from using the built in web server to using apache2 (or
whatever, I have apache2 on my system).
Too simple for me, it doesn't run.....
chris$ python manage.py runserver
Error: No module named addition.addnums
chris$
My own working through the tutorial does though:-
chris$ python manage.py runserver
Validating models...
0 errors found
Django version 1.2.3, using settings 'djdb1.settings'
Development server is running at http://127.0.0.1:8000/
Quit the server with CONTROL-C.
--
Chris Green
I was semi joking, I realise that this *isn't* how it works but so far
I'm not at all clear how it does work.
--
Chris Green
Yes, I'm not complaining at all, the feedback has all been very helpful.
I'm just rather impatient when I start trying to use something new. :-)
So, thank you everyone who has replied, I do appreciate all the help.
.... and I will continue through the tutorials. :-)
--
Chris Green
you did not follow the instructions here:
https://bitbucket.org/lawgon/django-addition/wiki/Home
--
regards
Kenneth Gonsalves
Ah, OK, I did look around for some instructions but didn't find them.
Thank you, I'll go and play some further! :-)
--
Chris Green
I have put the instruction on the front page - thanks for the heads-up.
--
regards
Kenneth Gonsalves
--
Chris Green