On 18/10/2011 8:45, Kevin wrote: > Hello everyone! > > I have been using Django for about a year now and feel that I want > to take my experience to the next level. I have created a few website > using Django to test my skills, although not for anyone specific. I > am creating this thread as I will like to ask current Django website > developers what tools and apps are crucial to be learned. > > Currently I have been focusing on the following: > > * Django 1.2 > * Django-guardian > * JQuery(although not specific to django) > * Pyjamas(nice alternative to GWT and works with django) > * Began learning Pinax(based on Django 1.1) > * Began learning Django-cms > * A few other, but cannot remember off the top of my head. > > The problem is that I'm not really sure what Django apps to learn due > to the overwhelming amount of apps that do the same thing, just > differently. I choose Django-guardian over Django-authority, for > example. > > The next django app I plan on learning is Djax and Djaxice. > > Which Django apps does everyone use in their Django projects for your > company/clients? I'd rather not learn something which is either going > out of style, out of style, out dated, or barely used. I cannot take > this type of experience with me to work on a larger scale project. > > You must agree that when you look at the djangopackages website, there > are an overwhelming amount of apps which do almost the exact same > thing. I'm not sure how it feels the download counts, or the other > data. I would hope from PIP, but not sure if it has an open API for > polling download counts and such data about packages. >
Hi, I've seen a lot of posts dealing with what "technology" you should master but it's also important to think about how you should develop. Coding style is important, as often you work in a team. Nice to be able to read each others code. Same with documentation. Have you documented the projects you've made? Are you able to work on an old project without to much searching around, in other words, is your code clear enough to dive right in again? reStructuredText seems popular, I've used epydoc in the past. Make a choice on a versioning system. I use git. mercurial, subversion are also popular choices. Preferably, you'll be able to use at least git and subversion as they are widely used. What is your development environment going to be? For instance, virtualenv with pip is what I use. Will you use a Virtual Machine solution (VirtualBox, Xen, whatever... or containers like lxc) to split your production from development and staging? What tools are you going to use to publish your apps? Fabric is a nice option. Also, I tend to document my steps when I install such an environment. Always nice to know how the environment was setup. For development or staging, you have a number of options. Apache, nginx as webserver coupled with mod_wsgi or gunicorn for instance. Choose something that will work on the hosting you end up with and that you know so you can solve problems when they occur. If you pusblish an app, what provider will you use? You may want to be able to show the progress of the project to your customer. I'm sure there are other considerations as I only scratched the surface. Some of the tools/apps I use: - Debian ( 1st install was potato :)) - VirtualBox - nginx - gunicorn - supervisord (watch gunicorn process) - git - virtualenv - pip (coupled with virtualenv, it's a powerful tool) - south (easy db migration) - fabric (application deployment) - Django trunk (for development, I tend to use trunk as it's inhouse development) - Postgres db with psycopg2 python module - memcached - workzeug / django-extensions - django-registration ... Cheers, Benedict -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
