The project layout structure is great. All Django developers should follow this.
Our Django Book is Launched
41–50 of 136 posts
Re: Our Django Book is Launched
#42Nice! Will add it to the portuguese Python compendium i'm working on in my spare time https://gist.github.com/32d09bb884b3428c8fa7
Re: Our Django Book is Launched
#43Earlier quoted context omitted.
Disclaimer: I'm one of the authors. The book covers 7 pages that gets you started down the road of understanding security. We provide you the stuff you have to know, and point you towards better resources. Keep in mind we aren't professional security experts. If your site needs to be that secure, the best thing you can do is to hire the services of a carefully vetted security expert.
I think a great title for the security chapter should be Django Unchained. I look forward to reading this- Thanks.
ROFL
Re: Our Django Book is Launched
#44Considering purchasing since I was thinking of diving into django for my next project.. If I buy the PDF now, and you eventually release an EPUB or other format, will I get access to those files (with updates) as well?
Honestly, I don't know enough about ePub distribution to answer you. I would love to do that though.
Re: Our Django Book is Launched
#45One of my big concerns is user / session security. I have tried to follow and reason through discussions on stackoverflow and much of tpatchek's notes. I would be interested in how "high level" the security chapter is from anyone who has shelled out already. For example I assume I will 1. only use persona or openid (avoids storing passwords in my servers thus making a lot of things much much easier) 2. sessions - sto…
I'm not sure what this has to do with the focus of the book, Django has session support so I doubt a book about Django would fully cover re-writing one of its components. Django used to only be able to store nothing in the session cookie other than the ID so that part can definitely happen (new in Django 1.4 are Cookie Based Sessions that used signed cookies to store data in cookies, but it's something you have to tu…
A brief read of the sessions docs throws up three concerns
1. Stuffing a lot into a session cookie (the term can easily exceed he 4096 bytes limit suggests that this is not designed just to store session ids)
2. There is implication of one site secret key - a flaw in Flask which it's dangerous was supposed to fix - but even so there is the implication the MAC check guarantees No one has played with the cookie. This is flat eke bread and butter breaking those
3. It still is making the base assumption that the developer can willingly stick whatever he likes in a python duct and have that magically comeback from the client untouched - of that seems to be so.
Just I prefer having caching problems on my server than never knowing if the information from the cookie can be trusted
Re: Our Django Book is Launched
#46One of my big concerns is user / session security. I have tried to follow and reason through discussions on stackoverflow and much of tpatchek's notes. I would be interested in how "high level" the security chapter is from anyone who has shelled out already. For example I assume I will 1. only use persona or openid (avoids storing passwords in my servers thus making a lot of things much much easier) 2. sessions - sto…
If you're interested in security and have been following tptaceks notes, then no doubt you will have seen his recommendation for reading The Web Application Hackers Handbook.
I'm just a rank-and-file web developer, but I would also strongly recommend reading this book, regardless of what language or framework choice you've made.
Re: Our Django Book is Launched
#47Earlier quoted context omitted.
I'm not sure what this has to do with the focus of the book, Django has session support so I doubt a book about Django would fully cover re-writing one of its components. Django used to only be able to store nothing in the session cookie other than the ID so that part can definitely happen (new in Django 1.4 are Cookie Based Sessions that used signed cookies to store data in cookies, but it's something you have to tu…
A brief read of the sessions docs throws up three concerns 1. Stuffing a lot into a session cookie (the term can easily exceed he 4096 bytes limit suggests that this is not designed just to store session ids) 2. There is implication of one site secret key - a flaw in Flask which it's dangerous was supposed to fix - but even so there is the implication the MAC check guarantees No one has played with the cookie. This i…
Yes, if you change the defaults and don't read the docs it is possible to get in trouble.
Re: Our Django Book is Launched
#48Congrats Audrey! =)
Re: Our Django Book is Launched
#49It always puts a bad taste in my mouth when information/knowledge is locked behind a pay-wall. It frustrates me when I think that someone somewhere is getting turned down from what they want to learn from because they had no money to pay for it or doesn't have the means to pay for it. I know the authors should profit but why can't they do something like https://mitpress.mit.edu/sicp/ or http://debian-handbook.info/ or http://www.aosabook.org/en/index.html or http://philip.greenspun.com/seia/ or http://learncodethehardway.org/ or http://10print.org/ etc etc etc... Aren't the authors of these books making money? Or is it the fear that people just won't pay for it if its also free to download even if they can?
EDIT: I didn't 'click-through' to the book's original site because there was no mention that the book is also available to those who can't afford on this announcing page. My mistake.
Another great resource: http://gettingstartedwithdjango.com/ and videos here: http://gettingstartedwithdjango.com/pages/gigantuan/
Re: Our Django Book is Launched
#50It always puts a bad taste in my mouth when information/knowledge is locked behind a pay-wall. It frustrates me when I think that someone somewhere is getting turned down from what they want to learn from because they had no money to pay for it or doesn't have the means to pay for it. I know the authors should profit but why can't they do something like https://mitpress.mit.edu/sicp/ or http://debian-handbook.info/ o…
If you want the world to have a free book about Django, feel free to write one and make it public.