title: Django migrations not applying after moving from test PC to production server/DB
body: <p>I am unable to run the inital migrations in my django project on my production server.</p>
  
  <p>I started working on my Django app on my computer with a sqlite db. I was able to run the initial migrations (auth, admin, etc.) and they created tables in my sqlite db with no problem. I was also able to get tables created for the models in my app. </p>
  
  <p>Today I moved the same django project to my webfaction server via git and I am unable to get my MySQL db populated with tables at all. As soon as I created the db, I ran migrate but it said there were no migrations to apply. I tried deleting the migrations folder in my app, but that didn't help at all, probably because there is no django_migrations table to compare any migrations against. </p>
  
  <p>It seems as if the initial migrations are stored where django is installed. This is not part of my git repo, so anything there that might indicate whether the migrations have been made wouldn't be pulled over. </p>
  
  <p>I tried running <code>python manage.py migrate admin</code>
  And the same thing with auth, but it did't work</p>
  
  <p>I'm not really sure what the proper way is to go about getting these initial migrations to run again so that I have the proper auth and admin tables in my db. Any help would be appreciated. </p>
  
  <p>This is Django 2.1.7 and Python 3.5</p>
  
  <p>Thanks, Yongjin and Nagesh. By asking me to post my DB settings, you made me realize that I hadn't changed the name of the DB from the project I copied the settings from. Much appreciated!</p>