[Fixed] Local setup issue

[sree-hari-s]

#6
The issue was because the migrations file was ignored by the .gitignore file

I have updated the .gitignore file and also added the migrations files

[nfoert]

Hi there, thanks for the PR. If you check the .gitignore, I'm already ignoring the migration files, so this change is not necessary.

Check this commit

[sree-hari-s]

Hi there, thanks for the PR. If you check the .gitignore, I'm already ignoring the migration files, so this change is not necessary.

Check this commit

Hey I am actually mentioning to not ignore the migration files. because that was what led to the issues for local setup.

Check this link

[nfoert]

Hi there, thanks for the PR. If you check the .gitignore, I'm already ignoring the migration files, so this change is not necessary.
Check this commit

Hey I am actually mentioning to not ignore the migration files. because that was what led to the issues for local setup.

Check this link

Ok, I understand what you mean now, and I see the benefits.
Some people were having trouble with the migrations and a fix was to remove them, I think there may be a larger problem going on instead. I'll do a few tests and merge this in a bit.

[nfoert]

Well, it looks like everything is working as expected. If anyone else is having trouble when setting up their server please comment here, there may still be an issue that I'm just not encountering.

Thanks for working on this @sree-hari-s!

[nfoert]

I did end up encountering an error, but I do have a fix for it.
My error seemed to be a conflict between the migrations and the database:

django.db.utils.OperationalError: duplicate column name: current_conversation_id

I was able to fix it by running this command:

python manage.py migrate --fake

This seems to fake the migration system into thinking that all of the necessary migrations have been applied, and therefore causes the database and the migrations to be up to date. (Correct me if I am wrong :D)
Thanks to this answer for helping me out.