I have a django app connected to postgresql database (RDS instance running on AWS)
Recently, I added new fields to my database tables, but forgot to run makemigrations locally and pushed the code to the server. The server went down since changes were not applied, and in order to fix the problem quickly I decided to run makemigrations and migrate directly in docker container of the application, I thought it would generate migration files, but unfortunately, it didn't. The migration was applied on database level, but there is no migration file of the changes.
When running python manage.py showmigrations in the container, it outputs:
redirect
[X] 0001_initial
[X] 0002_redirect_clicks
[X] 0003_redirect_name
But in database, running SELECT * FROM django_migrations; tells that there is one more migration:
103 | redirect | 0004_auto_20210707_2039 | 2021-07-07 14:39:19.058233+00
What would you advise? I thought of running makemigrations locally, generate the file and push it to vcs, and on the server apply the changes using migrate --fake.
I don't know what this does exactly and I am too scared to do it without guidance, any help would be appreciated