Hello,
I am talking about even more basic than this.
◾ Should I use Apache, Gunicorn, uWSGI or something else?
Honestly I have only heard of Apache and have only seen Gunicorn in
relation to Mezzanine. I have no idea what Gunicorn is!
◾ Where should I use caching to make things faster?
I know this because I've been building WordPress websites for about a
year now, so sometimes I need to worry about caching, but how to do this
with Django, I have no idea.
◾ How do I know if my database has the right indexes or if it needs more
resources?
Frankly, I know nothing about DBs other than sqlite is a nice place to
store data and is an alternative to pickling if one wishes to save lots
of data across sessions. I know most places use My SQL, but I've never
seen any reason to go away from sqlite and I just do it because people
say I should.
◾ Do I need a NoSQL database like MongoDB?
What is MongoDB?
◾ The site runs great on my laptop. Why is it so slow in production?
Erm because you either are running off your home computer which needs to
send data through your personal router or because your server is horrible.
◾ How many servers does my site need? How big should they be?
I never considered a site would need to have more than 1...
◾ What is the 20% effort that will solve 80% of my performance problems?
Probably using python and brython rather than PHP and Javascript...
So I know python really well, I just know nothing about web development.
The most difficult parts of django are figuring out how get and post
work, writing templates, dealing with the DB API and deploying.
The building your first app in django tutorial is great, but I kind of
would like a couple more completely different apps. I just don't
understand how the web works from such a short tutorial.
Django claims that it is not magic, but for me, most of it is magic at
this point. Sometimes the connections are really difficult to follow.
Sometimes I don't want to know some of the connections, I just want to
know what they do and why. It is like event queues in a game engine. One
doesn't need to know what kind of event queue the engine is running in
order to capture the different events or how they use different threads
to grab input, but I do need to know that when the user hits enter my
on_input or my on_keydown function will run.
But when people throw around terms like Ajax, caching, Gunicorn, uWSGI,
database, URI, canonical request or anything like that, people who have
never worked with the web kind of nod and say oh yeah, yep! What ever
you say!
So I would say the tutorial you pointed to looks like an intermediate or
advanced newbie tutorial. Not really basic at all.
Thanks,
Brandon Keith Biggs <http://www.brandonkeithbiggs.com/>
On 7/22/2015 5:04 AM, JJ Zolper wrote:
Brandon,
I think we may be talking about different aspects of running a
website. Using a CMS is another topic in relation to what I was aiming
for.
I'm referring to the skills involved in managing the server
infrastructure of a live website, not managing the content of a live
website. I'm talking about things like Amazon Web Services, load
balancing, caching, and so on.
I got railed big time before because I suggest the community leverage
the skills of: https://highperformancedjango.com/.
Okay sure I get it the guy's at Lincoln Loop wrote the book and they
are best friends with the Django community, but I don't think that
should stop the community from either writing out own interpretation
of what it takes to be the sys admin of a live website at the
technology level. We need to begin working together to create
consensus and sharing knowledge. We need to begin learning from each
other in the public eye. If we want Django to be the best it can be we
need to have a real discussion about how we can go about writing docs
on the tools and skills needed for running a live Django website. I
don't care how the Django higher ups want to do it but I think it's
something we need to at least get the ball rolling on. I know it's
more work but it's something we can just keep iterating on as a
community slowly but surely.
Brandon, the only part I see being relevant to what this thread is
about is running a server for a game. For client vs server side you
would use AJAX / Javascript on the client and Django on the server
side. The scores thing is something you will have to do some research
on first. Learn the basics before you try to run.
JJ
--
You received this message because you are subscribed to the Google
Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to django-users+unsubscr...@googlegroups.com
<mailto:django-users+unsubscr...@googlegroups.com>.
To post to this group, send email to django-users@googlegroups.com
<mailto:django-users@googlegroups.com>.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/d605b9bd-be4e-456d-8610-df444b26fbd0%40googlegroups.com
<https://groups.google.com/d/msgid/django-users/d605b9bd-be4e-456d-8610-df444b26fbd0%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/55AF1894.5060709%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
