Django Blog Apps

Here are some Django blog apps for those who are looking for blogging software written in Django / Python:

Byteflow

MightyLemon

Django basic apps

Labels: django

Byteflow - a Django Blog App

Byteflow is a django blog application.

Byteflow is a blog engine, written on Python, using Django. Why should you choose it over competitors? It has very clean codebase and developers, which are struggling to keep it so (that ease learning code and adding features for python programmers and those who sympathize ;). It has a lot of cool features, which you can't get in other blog engines or will get with difficulty (consider feed by union of tags, eh?). And of course it is actively developed so release are not that far away (we'll base on Django 1.0.1, which was released in November).

Labels: django

mightylemon - a django blog app

MightyLemon is a django blog app.Check out the readme.

Labels: django

Django shopping cart (Satchmo)

Found an open-source (BSD) Django shopping cart application called Satchmo. Haven't tried it out yet but looks intriguing. I like the stores it's powering including this cool tote bag store.

Here are instructions for installing Satchmo on WebFaction.

Labels: django

How to install mod_python on XAMPP

Complete tutorial for getting mod_python set up on XAMPP so you can work on Python and Django projects on your localhost computer.

Installing Python (mod_python) on XAMPP (on Windows)

XAMPP + Python + Django

Labels: django, python, windows

How to Use the Django Sites Framework

Instructions from the Django Book are skimpy.

How to Use the Sites Framework

The sites framework is more a series of conventions than a framework. The whole thing is based on two simple concepts:

The Site model, found in django.contrib.sites, has domain and name fields.

The SITE_ID setting specifies the database ID of the Site object associated with that particular settings file.

How you use these two concepts is up to you, but Django uses them in a couple of ways automatically via simple conventions.

To install the sites application, follow these steps:

Add 'django.contrib.sites' to your INSTALLED_APPS.
Run the command manage.py syncdb to install the django_site table into your database. This will also create a default site object, with the domain example.com.

Change the example.com site to your own domain, and add any other Site objects, either through the Django admin site or via the Python API. Create a Site object for each site/domain that this Django project powers.

Define the SITE_ID setting in each of your settings files. This value should be the database ID of the Site object for the site powered by that settings file.

Here's another clue.

And perhaps a better way to do this.

The official documentation.

The closest thign toa tutorial:

Next you’ll want to create separate settings files for each domain you’re adding; each one will need its own MEDIA_URL and other settings. You’ll also want to do two things to make sure everything works out properly for administering the different sites:

Create a new Site object in your admin for each domain, and put the id of that Site into its settings file as SITE_ID so Django knows which site in the database corresponds to this settings file.

In the settings file for your original site (the one with id 1), add the other sites’ settings files to the ADMIN_FOR setting, to let Django know that this one instance of the admin application will handle all of the sites.

Now you can use the single Django admin running on your domain to create weblogs which will show up on your friends’ domains.

A couple more leads:

deploying with django's sites framework on webfaction

Serving Multiple Hosts from a Single Django Instance

Labels: django, python

Django deployment articles

Creating my Dream Server for Django

http://lethain.com/entry/2007/jul/17/dreamier-dream-server-nginx/

Labels: django

memcached with django on windows

Installing Memcached for Django Application on Windows XP

Installing Memcache On Windows For PHP

Running memcached on Windows

memcached for Windows - v.1.2.4

memcached on jellycan - 1.2.6

memecache2 for win 32 - old version

Labels: caching, django, windows

Django deployment with version control using subversion

Django deployment with version control using subversion. Part of a longer series on the topic of Django web development.

Labels: django, version control

Easy Django deployment with Fabric, a Capistrano-like utility

Capistrano itself can be used to deploy Rails apps, but there is a Python equivalent known as Fabric:

Fabric: simple pythonic deployment.

Fabric user guide.

Labels: django

Django deployment using Git and Fabric

Good articles by Will Larson on deploying Django apps using Git and Fabric:


Deploying Django with Fabric



Installing a Development Deployment of LifeFlow, a Django Blog Solution

Labels: django, fabric, git

Version control live websites using Git

Articles about using Git for deployment and versioning of live web sites:

Using Git to Maintain Your Website

Using Git to manage a web site

A web-focused Git workflow

And specifically for Django:

Development to Deployment in Django

A Tale of Three Repositories

The foundation of my development-deployment pipeline is three repositories (it's a bit simpler using distributed version control, but you could accomplish more or less the same with Subversion or CVS).

A master repository hosted in a non-local and non-production location. I use my Slicehost slice that hosts my blog for all my private git repositories (it has daily and weekly backups, and if it does lag or crash, I can fix it myself), but you could use a paid GitHub account or one of the other similar services.

A local repository for each developer, which they push out to the master server at regular intervals.

A production repository on each production machine serving the project.

Developers do most of their work on their local machines, and push it to an appropriate branch on the master repository. They also pull from the master server occasionally to keep the repositories synchronized.

The production repositories are kept up to date by either:

Using Fabric to command them to pull the newest changes. This is the best option for large, medium and small deployments. That is, this is always the best option. Don't bother reading the others.

SSHing into the production servers and manually pulling the change set. Alternatively you could write a batch script that does this. This approach is more than sufficient for one machine deployment, but for anything more complex than that you'll want to use a deployment solution.

Setup a cronjob that pulls the changes periodically. This is the simplest and laziest of the approaches, but is a bad idea in most circumstances.

That's a good article.

Labels: django, git, version control

Django on Hostgator (How to Install)

Here are the instructions for installing Django on Hostgator shared hosting.

I've successfully installed Django on my Hostgator account ('Baby Croc' plan) using these steps. Hostgator has been really great for me, but they don't support fastCGI. Using vanilla CGI with Django is not generally recommended and results in crappy performance, but for a low traffic site it's bearable (barely).

I have to say that the instructions make it look pretty hard to deploy Django, but I think this may come in useful someday! Thanks to whoever wrote this. Apparently that was written in August, 2007. So no new updates since then. The thread on Hostgator forums seems pretty much dead, which is disappointing. I'm sure a lot of people are interested in hosting Django sites on Hostgator. Hopefully the Hostgator people will respond and support FastCGI.

If you have experience hosting Django on Hostgator please leave a comment. Thanks.

Labels: django, hostgator

How to Install and Run Django on Windows (Vista)

Download the Django file from the website.

It's tarred and gunzipped, so use 7-zip to extract it.

Put the extracted directory somewhere.

In your console, cd to the directory (Django-0.96.1 or whatever).

Run this command in the console:
python setup.py install

Start python by typing 'python' at the command line.

Then type:
>>> import django
>>> django.VERSION
(0, 96.099999999999994, None)

Add to your path (see my post about setting path in Vista):
c:\Django-0.96.1\django\bin

You may need to restart console if the path doesn't update (if you changed it via windows see my blog post.)

Then do:
C:\django_projects>django-admin.py startproject mysite

that creates the directory with 4 python files

mysite/
__init__.py
manage.py
settings.py
urls.py


Then start the server that it comes with:

C:\django_projects\mysite>python manage.py runserver
Validating models...
0 errors found.

Django version 0.96.1, using settings 'mysite.settings'
Development server is running at http://127.0.0.1:8000/
Quit the server with CTRL-BREAK.


Now go to:
http://localhost:8000/

Now you have Django on Windows!

Labels: django, python, windows