61–70 of 75 posts
Wow, this looks really good. A decent django tutorial that covers all the ops side is somewhat lacking I feel, and this certainly looks pretty full. How do you plan to fund the other lessons?
The Kickstarter is funding all 10 originally planned episodes plus ~5 more covering FAQ-type situations.
chef, vagrant, ubuntu, apt-get, pip, virtualenv, heroku, ssh.. oh there it is, sth about learning django. I'm saying it not to diss your work, but don't you think setting up a linux env on a vm and signing up to heroku shouldn't be the point of a django tutorial? point explained in another discussion about zed's approach to writing 'learn x the hard way' https://news.ycombinator.com/item?id=4961593
One of the thing I usually find hardest about trying out any new web-stack is not necessarily writing the code but wrangling with all the ecosystem BS around it. It's nice for a tutorial to acknowledge this and give you a VM to play around with.
But put it at the end of the tutorial, not at the beginning
Come on guys, they're doing the tutorial to learn Django, not "all the things around it" (which are important, but it is not Django).
Earlier quoted context omitted.
One of the thing I usually find hardest about trying out any new web-stack is not necessarily writing the code but wrangling with all the ecosystem BS around it. It's nice for a tutorial to acknowledge this and give you a VM to play around with.
Yes this is hard. In Django especially, not very easy for beginners. But put it at the end of the tutorial, not at the beginning Come on guys, they're doing the tutorial to learn Django, not "all the things around it" (which are important, but it is not Django).
I agree that to learn a language you should not focus on "operational" stuff, but once you get into web frameworks that line can get a little blurry.
Earlier quoted context omitted.
I feel like that reasoning should be outlined in the tutorial. As a newbie, it seems like a pain to get django running if I have to set up a VM just to do it, and the author provides little explanation. Coming from rails, its weird to me that he seems to emphasize their 'gem install' equivalent over their bundler equivalent. Otherwise, a great tutorial.
That's because there isn't really a good "bundler equivalent" that I know of. That was one of the more frustrating parts of Python work for me. Virtualenv is kind of a hybrid between gem and bundler, and it works, but it's nowhere near as elegant.
This article covers some of the equivalent jobs using Ruby and Python:
http://gillesfabio.com/blog/2011/03/01/rvm-for-pythonistas-v...
The article misses covering the freeze command in pip which is great for generating requirements.txt files:
pip freeze > requirements.txt
Covered in detail here: http://www.pip-installer.org/en/latest/requirements.html
Earlier quoted context omitted.
Indeed, it's a good corollary. :-)
From Wikipedia: A corollary is a statement that follows readily from a previous statement. Huh?
http://www.merriam-webster.com/dictionary/corollary
check out the second definitions part a and b:
2.a : something that naturally follows : result
2.b : something that incidentally or naturally accompanies or parallels
Earlier quoted context omitted.
Perhaps a better title for the series would be "Getting Started with Django in the Real World" Because in the real world, you need to know things like chef, vagrant, ubuntu, apt-get, pip, virtualenv, heroku, ssh... if you want to do anything beyond building a demo app that only runs locally. I use all this stuff every day and I'm looking forward to going through this tutorial. I'm also quite excited about the prebuil…
I've built plenty of very real Django apps without any of these (except ssh). Heroku's not the only platofrm, Ubuntu's not the only OS. Neither are even significantly mainstream in the industry. This tutorial is so myopic. It reads more like a recipe from a beginner's cookbook than anything else.
Chef and vagrant are going a long way towards giving me most of the things I love about Heroku and dotCloud but with more control.
why is that HN crowd is so much into Django? Every day I see something Django-related on the top page. I feel like I'm left out... is Django like the world's number one web framework (for hackers)?
Earlier quoted context omitted.
The Kickstarter is funding all 10 originally planned episodes plus ~5 more covering FAQ-type situations.
Is it worth putting a link to the kickstarter on the front page? Would certainly help explain a lot about the project and if it's still running people can chip in.
Is there a way to save HN stories, aside from commenting on them? I don't want to leave a pointless comment just so I can find it later (I didn't want to leave this one.).
While others are complaining about all the up front set up; this is actually something I like. Base tutorials always seem to be missing that 'something' that takes what you've learned and turns it into a real world application. Even if its not step one, I would prefer more tutorials to have a full fledged 'Getting Set Up' section; even if it becomes arbitrary. It makes sure everyone can get on the same page no matter…
I agree, and in this case it's setting up a very consistent environment that will be almost exactly the same as the one he's going to be using. Additionally, these are the actual procedures you could use to set up a very real and serious tool. I'm loving this!