Home > Django, Satchmo > Satchmo installation

Satchmo installation

November 14th, 2011 Leave a comment Go to comments

Been playing with Satchmo today. One issue I ran into, is I installed the Trunk version of Django, which Satchmo apparently isn’t compatible with; it apparently expects Django 1.3. The easiest way to get started with a very fresh install of Satchmo is to go through the following steps.

Setup and activate virtual environment:

~/projects$ virtualenv test
~/projects$ cd test
~/projects/test$ source bin/activate

Make sure you have PIL installed:

sudo apt-get install python-imaging

Install Satchmo:

~/projects/test$  hg clone https://chris1610@bitbucket.org/chris1610/satchmo
~/projects/test$ cd satchmo
~/projects/test/satchmo$ python setup.py install

Install all the other requirements:

~/projects/test/satchmo$ pip install -r scripts/requirements.txt

Setup sample store

/projects/test$ python source/satchmo/scripts/clonesatchmo.py
/projects/test$ cd store
/projects/test/store$ python manage.py runserver

Then just shoot your browser to:

http://localhost:8000
Categories: Django, Satchmo Tags:
  1. November 14th, 2011 at 19:46 | #1

    I am not aware of a problem with Satchmo tip and Django trunk. What error are you seeing?

  2. November 15th, 2011 at 10:25 | #2

    Hi Chris, When I used trunk and then ran the clonesatchmo script there was an error “ingesting” the fixture data, which I don’t get with Django 1.3 (everything else being equal).

    ConstructorError: could not determine a constructor for the tag ‘tag:yaml.org,2002:python/long’

    satchmo_store.contact.models.DoesNotExist: ContactRole matching query does not exist.

  3. Hynek Cernoch
    November 16th, 2011 at 18:40 | #3

    It is fixed now in Satchmo. It has been caused by Django Changeset 17062 made in trunk 2 weeks ago. You was the first who reported it.

  4. November 16th, 2011 at 19:16 | #4

    Just as an FYI, we’ve updated the YAML fixture so it will work with the latest version of satchmo.

  5. November 16th, 2011 at 19:19 | #5

    Amazing response to that issue. Thanks a lot. Keep up the great work!

  1. No trackbacks yet.