The video was fairly long and I wish there was a way for specific sections in the video to be indexed so one can just to sections that are of interest. Then again the text transcript is below so I guess that's an easy way to look up what is needed. I am particularly interested in all the different ways developers set up their settings files. I use a solution which works but I always feel could be a bit more elegant as it requires passing a DJANGO_SETTINGS_MODULE variable when activating a virtualenv (different settings file is activated depending on whether it's a development, staging or production environment)... I think I copied this method from Zachary Voase's blog. Maybe the method you use is better for Heroku, I'm not sure.
Getting Started with Django
51–60 of 75 posts
Re: Getting Started with Django
#52Earlier quoted context omitted.
I'm running VirtualBox 4.2.4 but I would think, since it creates the VM when you `vagrant up`, that it wouldn't matter what version of VB you were running. So that's odd. The Vagrant version I have is 1.0.5, just for completeness sake. I just downloaded the zip file again to check, and there's nothing in there (at least that I can find) that mentions a version of VirtualBox. You're also the first person to mention a…
Looks like my problems were completely my fault. On my ThinkPad the virtualization setting is in the BIOS under Security and it was not set correctly. There were some other settings under CPU that I initially thought were the right ones. I'm sorry to waste your time.
Glad you found out what it was!
Re: Getting Started with Django
#53chef, 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
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.
Re: Getting Started with Django
#54While 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…
Exactly my thoughts. When I just started programming, there were so many tutorials I started on rails, django, and various other frameworks that I couldn't get to work the same way as in the tutorial. This was very important to me when I just started programming because if my results didn't match exactly that of the tutorials, I would not want to continue further since I am not sure if I am doing everything right.
One of the better tutorials I have found that takes extra care in making sure you are doing everything right, is the famous rails tutorial found here: http://ruby.railstutorial.org/ruby-on-rails-tutorial-book
Re: Getting Started with Django
#55Earlier quoted context omitted.
The plan is to do 1-2 per month, ideally about 1 every 2 weeks. I have to do them in my (and my editor's) off time, so some months that may slip.
Any chance you can add a subscribe by email form so we can be notified when you release new videos?
I've added a link to subscribe to the mailing list to the top of the site.
Re: Getting Started with Django
#56Earlier quoted context omitted.
I'm running VirtualBox 4.2.4 but I would think, since it creates the VM when you `vagrant up`, that it wouldn't matter what version of VB you were running. So that's odd. The Vagrant version I have is 1.0.5, just for completeness sake. I just downloaded the zip file again to check, and there's nothing in there (at least that I can find) that mentions a version of VirtualBox. You're also the first person to mention a…
Looks like my problems were completely my fault. On my ThinkPad the virtualization setting is in the BIOS under Security and it was not set correctly. There were some other settings under CPU that I initially thought were the right ones. I'm sorry to waste your time.
[deleted]
Re: Getting Started with Django
#57Step 1. Unchain him.
Re: Getting Started with Django
#58Earlier 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.
I've also built plenty of Django projects without a lot of the mentioned utilities, but that doesn't make them any less useful or recommended. I'm certain the developer knows that Ubuntu isn't the only OS and Heroku isn't the only deployment platform. I'd argue against the mainstream statement. Ubuntu is one of the more popular server distros used. Do you expect someone to cover every possible platform and PaaS provider?
What Kenneth is offering is obviously a guide with recommendations and not requiring you to use them for your projects. It's ultimately up to the developer to decide what to use.
Re: Getting Started with Django
#59Is 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.).
Upvote it and it will show in your "Saved Stories" page (link on your profile page).
I don't think it works for me. Maybe I don't have enough Karma or it is a bug. http://news.ycombinator.com/item?id=4462292
Re: Getting Started with Django
#60Earlier quoted context omitted.
This seems to be the perfect video to get setup before reading your book, which is very light on the "proper setup". I imagine that a book might not be the best format for that, or simply that this is not the content your main audience expect to start with.
Indeed, it's a good corollary. :-)
From Wikipedia:
A corollary is a statement that follows readily from a previous statement.
Huh?