Web Design Stockholm, Graphic Design Stockholm - ApPeL » Development

Django Nginx Centos 5

Arno Smit — Mon, 26 Sep 2011 08:49:19 +0000

From our earlier installation we went ahead and set up a CentOS box running Django, Apache and mod_wsgi. – you can view that here

Doing a bit of digging around, I have found some substantial information showcasing that Nginx is a much better choice for Django than Apache.

In order to make Nginx work, we need some sort of wsgi combined with Nginx, the easiest way to get this done is to install FLUP

/opt/python2.6/bin/pip install flup

Now let’s go ahead and create another user that will run a separate process, and also allow us to debug easier if something goes wrong.

Add Nginx user

useradd nginx passwd -d nginx

Install Nginx

yum install nginx cd /etc/nginx/ mv nginx.conf nginx-backup.conf touch nginx.conf vi nginx.conf

NGINX config file example (make sure to replace /www/django_test1/mysite with your project root)

user nginx nginx; worker_processes 2; error_log /var/log/nginx/error_log info; events { worker_connections 1024; use epoll; }


http {

    include /etc/nginx/mime.types;

    default_type application/octet-stream;
    log_format main

    '$remote_addr - $remote_user [$time_local] '

    '"$request" $status $bytes_sent '

    '"$http_referer" "$http_user_agent" '

    '"$gzip_ratio"';
    client_header_timeout 10m;

    client_body_timeout 10m;

    send_timeout 10m;
    connection_pool_size 256;

    client_header_buffer_size 1k;

    large_client_header_buffers 4 2k;

    request_pool_size 4k;
    gzip on;

    gzip_min_length 1100;

    gzip_buffers 4 8k;

    gzip_types text/plain;

    output_buffers 1 32k;

    postpone_output 1460;
    sendfile on;

    tcp_nopush on;

    tcp_nodelay on;
    keepalive_timeout 75 20;
    ignore_invalid_headers on;

    index index.html;

server { listen 80; server_name localhost; location /media/ { root /www/django_test1/mysite; # Replace with your own project root } location /mediaadmin/ { alias /opt/python2.6/lib/python2.6/site-packages/django/contrib/admin; # Alias to where our admin media root lives } location / { # host and port to fastcgi server fastcgi_pass 127.0.0.1:8080; fastcgi_param PATH_INFO $fastcgi_script_name; fastcgi_param REQUEST_METHOD $request_method; fastcgi_param QUERY_STRING $query_string; fastcgi_param CONTENT_TYPE $content_type; fastcgi_param CONTENT_LENGTH $content_length; fastcgi_pass_header Authorization; fastcgi_intercept_errors off; } access_log /var/log/nginx/localhost.access_log main; error_log /var/log/nginx/localhost.error_log; } }

If you are running a prior version of apache make sure to stop it.
/etc/init.d/httpd stop

Start my FastCGI

cd /www/django_test1/mysite/ python manage.py runfcgi host=127.0.0.1 port=8080 --settings=settings /etc/init.d/nginx start

Now that we have moved away from Apache we need to make sure that apache doesn’t switch back on when we restart the server for any needs.

chkconfig httpd off chkconfig --add nginx chkconfig --level 2345 nginx on chkconfig --list nginx

Python 2.7, OS X Lion and PIL, _imaging and Image

Arno Smit — Thu, 21 Jul 2011 10:07:36 +0000

My default version of Python was still on 2.6 so I had to switch to 2.7

defaults write com.apple.versioner.python Version 2.7

get v8c of jpeg
cd into jpeg directory.

sudo make clean CC="gcc -arch i386" ./configure --enable-shared --enable-static make sudo make install

get imaging i am using 1.1.6

untar
cd into imaging
sudo rm -rf build vi setup.py JPEG_ROOT = libinclude(“/usr/local/lib”) sudo python setup.py install

And it’s that simple

Run your python interpreter,

import PIL import _imaging import Image

if all is well, then your all set.

SAK konstföreningen

Arno Smit — Tue, 17 May 2011 08:11:45 +0000

Over the past few months we have been working very closely with SAK in order to move their old site over to a new one that makes a lot more sense.

We started this project with some inside knowledge on how the site was built but it ended up being bigger than Ben Hur.

The old site consisted of real old technology and all their records were kept in excel spreadsheets… not very good

So first of all we have to map out the relationships between the different sections of the site, and then we had to build a very intricate php extractor that took all of the data and mapped it over to a wordpress compatible db.

Many hours later we extracted all their data, built and re-imported all their images.

Here is the final results SAK – Sveriges Allmänna Konstförening

My-hunt.com – a social network for hunters, outfitters

Arno Smit — Wed, 16 Mar 2011 08:19:15 +0000

Over the last summer I spent most of my time working on one of my greatest achievements to date – my-hunt.com

My-hunt.com is a social experience/experiment for hunters that allows them to upload their hunting trophies, write hunting reports, learn more about the animals you hunt and also a friendship network.

Through the signup process you can choose whether to be seen as a hunter or whether you want to publish information about your hunting grounds.

We are very excited to introduce this into the market and look forward to expanding and introducing new segments every step of the way.

My-Hunt.com online, WE ARE HUNTING!

KeyError raised when using images with NON-ASCII filenames

Arno Smit — Mon, 07 Mar 2011 07:27:06 +0000

I recently created a django app that allows you to create projects, raise funding via social networks etc.

Because this is mainly based in Sweden we have to allow users to make use of NON-ASCII characters such as å ä ö and many other.

Easy way to get around this is to install UNIDECODE which handles all of this for you.

Each section/file you are going to make use of this remember to import unidecode

# Import of transliteration module from unidecode import unidecode

To install
pip install Unidecode

Then clean your picture in your forms.py
def clean_picture(self): data = self.cleaned_data['picture'] # For correct uploading non-ASCII image_filenames, we use transliteration module: unidecode() # can be downloaded here: < git clone http://code.zemanta.com/tsolc/git/unidecode > # Don't forget to import it: from unidecode import unidecode trans_name = unidecode(data.name) data.name = trans_name return data

And in your views.p that handles the actual saving

if form.is_valid(): # For correct uploading non-ASCII image_filenames, we use transliteration module: unidecode() # can be downloaded here: < git clone http://code.zemanta.com/tsolc/git/unidecode > # Don't forget to import it: from unidecode import unidecode cleaned_form = form.cleaned_data trans_name = unidecode(cleaned_form['profile_picture'].name) cleaned_form['profile_picture'].name = trans_name

mod_pagespeed CentOS 5.4

Arno Smit — Fri, 12 Nov 2010 10:24:06 +0000

Installing mod_pagespeed on CentOS 5.4

wget https://dl-ssl.google.com/linux/linux_signing_key.pub
rpm –import linux_signing_key.pub

32BIT

wget https://dl-ssl.google.com/dl/linux/direct/mod-pagespeed-beta_current_i386.rpm

64BIT

wget https://dl-ssl.google.com/dl/linux/direct/mod-pagespeed-beta_current_x86_64.rpm

yum localinstall mod-pagespeed-*.rpm

/etc/init.d/httpd restart

vi /etc/httpd/conf.d/pagespeed.conf

ModPagespeed on

Uncomment # ModPagespeedRewriteLevel CoreFilters

restart apache

Uncomment # ModPagespeedEnableFilters collapse_whitespace

Go to the google code page and find a list of items in their.

Play around with it a bit and find your best solution.

The full list of available filters, plus descriptions of how they work and how to use them, is available on the project’s Google Code page

Nynasbo Campaign Site

Arno Smit — Mon, 13 Sep 2010 10:02:35 +0000

Just recently did a small campaign site for Nynasbo making use of some jQuery ajax, this site was built in PHP and also makes use of The Dabber Player.

The Dabber Player

Arno Smit — Wed, 01 Sep 2010 10:00:10 +0000

Today sees the launch of the long anticipated “Dabber Player”.

A flash video player that combines the strength of video encoding and Amazon’s S3 services.

The player allows you to create different player with different looks and feels to suite your personality/brand look and feel, video upload and encoding all with a few clicks via your WordPress admin.

Free and Commercial version available now for download – http://bit.ly/9cmTvk

A working copy, Django, PIL, Imaging, libjpeg, mysql, git, apache, mod_wsgi, easy_install, pip, django-imagekit, cdn storage on CentOS 5.4

Arno Smit — Wed, 07 Jul 2010 14:29:59 +0000

Install Apache, MySQL, SQLite, and other developer packages

yum install httpd-devel mysql mysql-server yum install mysql-client mysql-devel yum install apr-devel sqlite3 sqlite-devel yum install libjpeg libpng gcc make autoconf yum install libxslt gettext zlib-devel yum groupinstall “GNOME Desktop Environment” yum groupinstall “Development Tools”

This tutorial will assume that you are using MySQL on production and you may also use SQLite for development. If you are using another database like PostgreSQL then you should install those files now. Also, please note that these are not the only packages that you will need for your webserver, this should just be considered a minimum to get your django app working.

Add New User

groupadd webmaster useradd -c “username” -g webmaster -m -s /bin/bash username passwd username passw0rd visudo
Near line 77 where it reads “root ALL=(ALL) ALL add
username ALL=(ALL) ALL

From here you can change to your user to leave the root account as is.
If you find that some of the item do not want to run you should use the sudo command

Install Python 2.6 along side of Python 2.4

The trick to getting Python 2.6 working on CentOS 5.4 without breaking anything is to install it along side of the default Python 2.4. Do not try to update your default Python 2.4 because important CentOS modules require 2.4. To do this you will configure python to be installed in /opt/python2.6. Before you do this step make sure that you have yum installed sqlite-devel because python will look for the sqlite header files in order to build the module for it when you compile python.

wget http://www.python.org/ftp/python/2.6.4/Python-2.6.4.tgz tar -zxvf Python-2.6.4.tgz cd Python-2.6.4 ./configure --prefix=/opt/python2.6 --with-threads --enable-shared --with-zlib=/usr/include make make install cd ~

After Python is installed in /opt/Python2.6 you need to create symbolic links to it.

ln -s /opt/python2.6/lib/libpython2.6.so /usr/lib ln -s /opt/python2.6/lib/libpython2.6.so.1.0 /usr/lib ln -s /opt/python2.6/bin/python /usr/local/bin/python ln -s /opt/python2.6/bin/python /usr/bin/python2.6 ln -s /opt/python2.6/lib/python2.6.so /opt/python2.6/lib/python2.6/config/

Run the ldconfig to update the links to your shared libraries and then check your python version to make sure you can now use 2.6. Also, test to see if there are any conflicts between Python 2.4 and 2.6 using yum. If you do have problems then double check your symbolic links and make sure that you are not conflicting with /usr/bin/python or /usr/bin/python2.4.

/sbin/ldconfig -v python -V yum info httpd

Install setuptools, MySQL extension, and Django 1.1

If you previously installed setuptools but you will need to do again for 2.6 so that the packages are installed in /opt/python2.6. In order to use MySQL with Django you will need to download, build, and install the extension for it.

wget http://bit.ly/6E0DNN chmod u+x setuptools-0.6c11-py2.6.egg ./setuptools-0.6c11-py2.6.egg --prefix=/opt/python2.6

wget http://bit.ly/6j4uID tar -zxvf MySQL-python-1.2.3c1.tar.gz cd MySQL-python-1.2.3c1 python setup.py build python setup.py install cd ..

wget http://www.djangoproject.com/download/1.1.1/tarball/ tar -zxvf Django-1.1.1.tar.gz cd Django-1.1.1 python setup.py build python setup.py install cd ..

Setup and Install mod_wsgi

A majority of the Django community uses wsgi as the way to interface with the webserver. I also prefer to use it because it’s fast and very easy to setup. This tutorial will not go into setting up your app to use wsgi (however, I will give an example at the end), but the django project has a good tutorial for this. Please note that this step is very important. You may have previously installed mod_wsgi using yum but you will need to download it and build it using your new 2.6 in order for it to work with your app.

wget http://modwsgi.googlecode.com/files/mod_wsgi-2.8.tar.gz tar -zxvf mod_wsgi-2.8.tar.gz cd mod_wsgi-2.8 ./configure --with-python=/usr/local/bin/python make make install cd ..

Then you will need to edit your Apache httpd.conf in order to load the mod_wsgi module. After this has been completed restart Apache.

vi /etc/httpd/conf/httpd.conf LoadModule wsgi_module /usr/lib64/httpd/modules/mod_wsgi.so line 787 AddHandler wsgi-script .wsgi

Make sure your Apache restarts once the module has been loaded

/etc/init.d/httpd restart

Create a separate directory for your virtual hosts

I like to house all my vhosts in a seperate directory

cd /etc/httpd/conf mkdir vhosts cd vhosts vi mysite.com.conf

ServerName localhost

ErrorLog /www/django_test1/mysite/logs/error_log CustomLog /www/django_test1/mysite/logs/access_log combined

UseCanonicalName Off

Alias /media/ "/www/django_test1/mysite/media/" Order allow,deny Options Indexes Allow from all IndexOptions FancyIndexing

Alias /mediaadmin/ "/opt/python2.6/lib/python2.6/site-packages/django/contrib/admin/media/" Order allow,deny Options Indexes Allow from all IndexOptions FancyIndexing

WSGIScriptAlias / /www/django_test1/mysite.wsgi WSGIDaemonProcess mysite processes=7 threads=1 display-name=%{GROUP} WSGIProcessGroup mysite WSGIApplicationGroup %{GLOBAL}

Create your mod_wsgi file

According to a few searches I have done online it is best practive to leave your mod_wsgi file in the parent folder of the app.

mkdir /www cd /www mkdir django_test1 cd django_test1 vi mysite.wsgi

#!/opt/python2.6/bin/python

import os, sys

sys.path.append('/www/django_test1/mysite') sys.path.insert(0, '/www/django_test1') sys.path.insert(0, '/www/django_test1/mysite')

os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' os.environ['PYTHON_EGG_CACHE'] = '/www/django_test1/mysite/.python-eggs'

import django.core.handlers.wsgi

application = django.core.handlers.wsgi.WSGIHandler()

Save the file

Create a .python-eggs directory

in mysite

mkdir .python-eggs chmod -R 777 .python-eggs

http://mikecantelon.com/story/installing_django_on_centos_5

Start the mysql server

/etc/rc.d/init.d/mysqld start

Install PIL on CENTOS

http://athenageek.wordpress.com/2009/06/09/easy_install-pil-not-so-easy/

Install PIP in order to use Imaging

/opt/python2.6/bin/easy_install-2.6 pip

/opt/python2.6/bin/pip install http://effbot.org/downloads/Imaging-1.1.6.tar.gz

Install GIT

http://www.bitsandpix.com/entry/git-installing-git-on-centos-5/

rpm -Uvh http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-3.noarch.rpm yum install git

Configure MySQL with another user

mysql --user=root mysql CREATE USER 'webdev'@'localhost' IDENTIFIED BY 'password'; GRANT ALL PRIVILEGES ON *.* TO 'webdev'@'localhost' IDENTIFIED BY 'password' WITH GRANT OPTION;

Create a Django project

/opt/python2.6/bin/django-admin.py startproject mysite

Create a logs directory in your project as this is needed for mod_wsgi and apache

cd mysite mkdir logs

Symlink your admin media folder

mkdir media chmod -R 777 media mkdir mediaadmin

ln -s /opt/python2.6/lib/python2.6/site-packages/django/contrib/admin/media /www/django_test1/mysite/mediaadmin/

Configure your /etc/httpd/conf/httpd.conf file to include your projects base settings

ServerAdmin admin@appelvm01.centos HostName appelvm01.centos

ServerName 127.0.0.1

DocumentRoot "/www/django_test1/mysite"

AllowOverride None Options None Order allow,deny Allow from all

# include VirtualHosts config files Include conf/vhosts/*.conf

add WSGISocketPrefix to httpd.conf end of file

WSGISocketPrefix /var/run/wsgi

Make sure hostname is equal to the one in Apache conf /etc/httpd/conf/httpd.conf
else change by running

hostname "new_name"

Give permissions

chcon -R -h -t httpd_sys_content_t /www/django_test1/mysite

I found this wasnt good enough so I had to turn off SElinux

vi /etc/selinux/config

set

SELINUX=disabled

According to a blog remove your -Indexes
http://www.thelinuxblog.com/apache-directory-index-forbidden-by-options-directive/

vi /etc/httpd/conf.d/welcome.conf # -Indexes Indexes

Configure Firewall

sudo vi /etc/sysconfig/iptables-config
Make sure following variables are set to “yes”:
IPTABLES_SAVE_ON_STOP="yes" IPTABLES_SAVE_ON_RESTART="yes"

Open Web ports:

sudo /sbin/iptables -I INPUT -p tcp -m state --state NEW,ESTABLISHED --dport 80 -j ACCEPT sudo /sbin/iptables -I INPUT -p tcp -m state --state NEW,ESTABLISHED --dport 443 -j ACCEPT
Restart iptables with:
sudo /sbin/service iptables stop sudo /sbin/service iptables start
Make sure rules are still in. Try restarting server, too, to make sure setting picked up.

Make sure your MySQL and Apache are always on after restart

/sbin/chkconfig --add httpd /sbin/chkconfig --level 2345 httpd on /sbin/chkconfig --list httpd

/sbin/chkconfig --add mysqld /sbin/chkconfig --level 2345 mysqld on /sbin/chkconfig --list mysqld

Install South through easy_install to allow for easy db migration

/opt/python2.6/bin/easy_install-2.6 South

Install Django-cumuls for Rackspace/CDN storage

/opt/python2.6/bin/pip install django-cumulus

/opt/python2.6/bin/pip install -r http://bitbucket.org/richleland/django-cumulus/raw/0.3.3/requirements.txt /opt/python2.6/bin/easy_install-2.6 django-imagekit

You should now be able to go to your servers ip address, and you should see a welcome screen!

From here on you can start developing your app, you should be able to enable your admins autodiscover and set the urls so that you can access the admin section.

libjpeg, PIL, Snow Leopard, Python2.6, _jpeg_resync_to_restart

Arno Smit — Mon, 21 Jun 2010 13:48:32 +0000

Man this has been an error that has been getting me down lately.

I have done tons of google searches for c _imaging not installed, PIL, libjpeg, Snow Leopard _jpeg_resync_to_restart and I have finally documented all my steps to rectify this issue.

If you don’t have this download it first.

http://www.ijg.org/files/jpegsrc.v7.tar.gz

go into your shell environment and untar by running the following

tar -zxvf jpegsrc.v7.tar.gz

cd jpeg-7

then run

./configuresudo make clean
sudo CC=”gcc -arch i386″./configure –enable-shared –enable-static
sudo make
sudo make install

Next get PIL and untar it

http://effbot.org/downloads/Imaging-1.1.6.tar.gz tar -zxvf Imaging-1.1.6.tar.gz cd Imaging-1.1.6

If you already have PIL I would recommend running

sudo rm -Rf build

to clean any existing builds, this has caused me loads of errors and gray hairs!

in your setup.py file run find JPEG_ROOT

amend it so it looks as follows

JPEG_ROOT = libinclude(“/usr/local”)

Next move onto the build

sudo python setup.py build

if libjpeg is successfully installed you should be able to run python selftest.py without any errors relating to “jpeg”

sudo python setup.py install

if all has worked successfully you should be able to enter your python interpreter by executing python in your command line and also do the following:

import PIL import Image import _imaging

without any errors.

Just to triple check I have a simple jpeg on my desktop.

image = Image.open(“/Users/MyName/Desktop/myimage.jpeg”) image.save(“/Users/MyName/Desktop/test.jpeg”)

should work without errors