id,summary,reporter,owner,description,type,status,component,version,severity,resolution,keywords,cc,stage,has_patch,needs_docs,needs_tests,needs_better_patch,easy,ui_ux 19741,Procedure in README.txt for setting up djangoproject locally doesn't work,Aymeric Augustin,nobody,"[originally reported by eswenson1 at https://github.com/django/djangoproject.com/issues/28] '''eswenson1''' The current procedures described in README.txt for setting up the djangoproject locally don't work. This appears to be because they assume that you already have a trac database setup properly with the correct schema. When the ./manage.py migrate step is executed, it fails due to missing relations from the trac model. In particular, the migration fails with the following error: Running migrations for trac: {{{ > Migrating forwards to 0001_initial. > trac:0001_initial ERROR: relation ""attachment"" does not exist STATEMENT: CREATE VIEW ""attachment_django_view"" AS SELECT ""type"" || '.' || ""id"" || '.' || ""filename"" AS ""django_id"", * FROM attachment; }}} Perhaps you could provide a truncated database dump from the live trac instance so that this can be used to create a dummy trac database. I decided to try to simply install Trac (0.12) and specify a database connection string that pointed to the code.djangoproject database. Once I did that, I was able to run the ""./manage.py migrate"" with no errors. The server started up fine after that. ''dlo''' Pull request: https://github.com/django/djangoproject.com/pull/46",Bug,closed,*.djangoproject.com,dev,Normal,fixed,,,Accepted,0,0,0,0,0,0