Django and Ensembl - part II

One thing I'll need to resolve going forward is the problem of read-only. The intent of ensembl is to use it 'as is', i.e in read-only mode. When Django starts a project and syncs the apps, it writes the default admin and auth tables into my ensembl db. Do I need these here? Do I need them at all? Can I set them up elsewhere?

If I don't want them or don't want them there, how best to make the db read-only? At the level of the MySQL db itself? Trusting that others won't abuse write privileges (yeah right)? Or in the Django code. I'm leaning towards the first option...