Yes, I can definitely understand the frustrations a PHP developer may have when moving away from it. PHP is very unique in that's it's one of the rare web technologies which has a deployment like it does. The original Active Server Pages and CGI also share the same deployment scheme. Usually programming languages which were not originally intended for the web use complex deployment structures, as seen with Python, Ruby, and ASP.Net. I am in agreement that deployment shouldn't be difficult. I have successfully deployed many Django powered websites, on private servers, and on cloud services such as RedHat OpenShift and PythonAnywhere. Kudos to PythonAnywhere for creating such a remarkable service, and their service will definitely be mentioned in the course. Originally I was going to focus the course around PythonAnywhere, where students would create an account there and do all their development in the cloud service. However, since I wanted to focus on the utter basics of the framework for at least the first couple chapters, I thought mentioning this service would take time away from actually learning Django.
Needless to say, there will be at least a couple chapters which provide a good basis for a successful deployment and how to troubleshoot issues along the way.
Best Regards,
Kevin Veroneau
PythonDiary.com
On Tuesday, 28 May 2013 16:37:06 UTC-5, Nikolas Stevenson-Molnar wrote:
Deployment in general is something you should be sure to cover.--
Especially when people are coming from the PHP world, deployment is
quite different. It seems like there are often questions on this list
around deployment problems, and they are often fairly trivial issues.
_Nik
On 5/28/2013 2:01 PM, Subodh Nijsure wrote:
> This is all IMHO.
>
> One of the thing that has been missing from many django books:
>
> How do you "marry" the current best practices for --deploying-- large
> scale web applications when using django.
>
> What are the best practices for enabling, monitoring caching?
> Implementing search using haystack or some other extensions?
> Would be interesting to find out, learn from best practices regarding
> how large software development teams work on django projects.
>
> -Subodh
>
> On Tue, May 28, 2013 at 11:34 AM, Kevin <kver...@gmail.com> wrote:
>> Sean,
>>
>> Thank you for your input. Having those types of examples would actually
>> be a great idea for the course, as these are some of the most popular
>> website being developed in our social web 2.0 these days.
>>
>> As for your thought on inputting financial data, I actually built a
>> personal financial manager in Django, and Django has the form facilities to
>> validate complex financial forms and tell the user to correct any issues
>> with their input. This would actually be a great idea for an example as
>> well, since Django manages form validation very well. I have this personal
>> application up on my BitBucket page if you wanted to take a look at it,
>> here's a link to the actual app:
>>
>> https://bitbucket.org/kveroneau/django-pim/src/ fffb63b6d03050b30d134bbe39d862 e5004a90da/pcbank?at=default
>>
>> Keep in mind that this app is some of my much earlier work, stuff I built
>> when I was first learning the framework. This was first built on Django 1.2
>> I believe, so it still does use function-based generic views. I do have it
>> running currently on a website, and use it all the time to manage my
>> personal financial data, such as bills and debt.
>>
>>
>> Best Regards,
>> Kevin Veroneau
>> PythonDiary.com
>>
>>
>> On Tuesday, 28 May 2013 12:29:20 UTC-5, SeanJ wrote:
>>> Kevin,
>>>
>>> Looking forward to what you come up with. I'd be willing to be a guinea
>>> pig for the course.
>>>
>>> First, I am a hobbyist developer (Java, Groovy/Grails, JS/Jquery/HTML5,
>>> PL/SQL, Python/Django), not a pro, and relatively new at it. My day job is
>>> a Software QA Manager for 40,000+ employee ERP Web App.
>>> Just for the fun of it I've been exploring Django. I've been through all
>>> the usual places on the web (djangoproject, djangobook, and others, and all
>>> the youtube tutorials) and I'm currently redeveloping 2 apps in django that
>>> I originally wrote in other languages/frameworks -- just as an exercise to
>>> see how django handles them.
>>>
>>> Second, My 2 cents on your outline and my request for content: I know
>>> with its newsy roots django excels in the blog/wiki/social posting space so
>>> there is a bit of glut in the django tutorial world for these types of
>>> examples, but I'm coming from a business web perspective and I don't find
>>> much out there on incorporating user number input (financial or other
>>> quantity) type data from forms which is then processed through some business
>>> logic in the view and redisplayed for validation by the user before being
>>> comitted to the database for storage.
>>>
>>> Apart from those 2 cents, your outline looks good. And I think JQuery is
>>> almost as much a part of the finished product as HTML these days. I think
>>> many will benefit from learning how to incorporate that library.
>>>
>>> Regards,
>>>
>>> Sean
>>>
>>> On Monday, May 27, 2013 3:02:58 PM UTC-7, Kevin wrote:
>>>> Hello everyone!
>>>>
>>>> It's been quite sometime since I have been on here, well I came back
>>>> with some great news! I am currently in the process of building an online
>>>> Django web course aimed at both new and old Django developers. I will be
>>>> charging a minimal fee for access to the entire course, but the first 3
>>>> chapters of the main sections will be free for everyone to read and enjoy.
>>>> The course software itself is built using Django naturally.
>>>>
>>>> The course software has been completed and uploaded online. I am now
>>>> in the lengthily process of writing up all the chapters, quizzes, example
>>>> code, and full projects. This is going to be a large amount of work,
>>>> however at the current moment this is my only job and that is why I am
>>>> planning on charging for admittance. I am aiming to have a large amount of
>>>> it completed by around the middle of June and ready for public consumption
>>>> shortly after.
>>>>
>>>> I have decided to give a lucky few free access to the entire course for
>>>> the purpose of reviewing and providing me with feedback. If you are
>>>> interested, please reply back to me and explain why I should select you. I
>>>> will then select 5 lucky individuals and email them their access credentials
>>>> and a link to the actual course's website when it's ready.
>>>>
>>>> Here's a little background information about myself, since I haven't
>>>> been on here recently. I am the current maintainer and author of
>>>> PythonDiary.com, which has been a relatively successful Python blog since
>>>> January of 2012. Over 500 users visit the blog each day, and if a new
>>>> article is available this amount can increase to over 1,000 hits. Many of
>>>> my articles and tutorials are related to Django, and most of my user base
>>>> uses Django or wants to learn it. I have received many requests from users
>>>> to expand on my Django tutorials, however I lack the personal time required
>>>> to write these articles. To that affect, I have ultimately decided to
>>>> create an entire Django web-based course for a very low cost. The cost is
>>>> much cheaper than a typical Django book available today and will touch on
>>>> more advanced concepts and also explain how to integrate and use popular 3rd
>>>> party Django apps. After reading many Django books, I always see them
>>>> missing on some key concepts or don't explain how to use particular 3rd
>>>> party apps. I have been building Django powered websites since around 2010
>>>> and have a large amount of experience with the framework that I can share
>>>> with others.
>>>>
>>>> Best Regards,
>>>> Kevin Veroneau
>>>> PythonDiary.com
>>>>
>> --
>> 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...@googlegroups.com .
>> To post to this group, send email to django...@googlegroups.com.
>> Visit this group at http://groups.google.com/group/django-users?hl=en .
>> For more options, visit https://groups.google.com/groups/opt_out .
>>
>>
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+unsubscribe@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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
No comments:
Post a Comment