Generate missing migrations

[naegelyd]

@yvandermeer cc @arpheno

Fix #19

There are three alterations happening in the migrations here. I will address each one separately:

1. Change the verbose_name on RequestParameter.name from naam to name.
2. Change the verbose_name on Response.content from inhoud to content.
3. Change the verbose_name on Response.content_type from inhoudstype to content type.

Without these alterations, one will see the following warning when trying to run migrations if httpproxy is in their INSTALLED_APPS.

Running migrations:
    No migrations to apply.
    Your models have changes that are not yet reflected in a migration, and so won't be applied.
    Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them.

This PR resolves that issue by adding the required migrations here to httpproxy.

[naegelyd]

Friendly ping @yvandermeer.

Any ETA in getting this reviewed and merged?

[yvandermeer]

@naegelyd Sorry for the delay in merging this. Thanks for your pull request!

[naegelyd]

@yvandermeer No problem. Thanks again for merging this in. Based on the timings on the releases, it looks like this change is in the 0.4.3 release. Could you push that release to pypi so we can pin our dependency to django-http-proxy==0.4.3 to make sure we get these migration changes?

[yvandermeer]

Yes, sorry, forgot to mention that. I just pushed the 0.4.3 release to pypi, ready for consumption. 👍

[naegelyd]

I just pushed the 0.4.3 release to pypi, ready for consumption.

Perfect! Thank you.