Heroku configuration ready

Author: Giovan

Pipfile

@@ -13,6 +13,10 @@ pygments = "*"
 httpie = "*"
 pyyaml = "*"
 coreapi-cli = "*"
+uwsgi = "*"
+django-heroku = "*"
+gunicorn = "*"
+pipenv-to-requirements = "*"
 
 [dev-packages]
 

Pipfile.lock

@@ -1,2 +1,2 @@
 release: python manage.py migrate --no-input
-web: uwsgi saleor/wsgi/uwsgi.ini
+web: gunicorn backend.wsgi

Procfile

@@ -9,7 +9,7 @@
 For the full list of settings and their values, see
 https://docs.djangoproject.com/en/2.1/ref/settings/
 """
-
+import django_heroku
 import os
 
 # Build paths inside the project like this: os.path.join(BASE_DIR, ...)
@@ -147,3 +147,5 @@
 # https://docs.djangoproject.com/en/2.1/howto/static-files/
 
 STATIC_URL = '/static/'
+
+django_heroku.settings(locals())

apiconfig/settings.py

@@ -0,0 +1,44 @@
+################################################################################
+# This requirements file has been automatically generated from `Pipfile` with
+# `pipenv-to-requirements`
+#
+#
+# This has been done to maintain backward compatibility with tools and services
+# that do not support `Pipfile` yet.
+#
+# Do NOT edit it directly, use `pipenv install [-d]` to modify `Pipfile` and
+# `Pipfile.lock` and then regenerate `requirements*.txt`.
+################################################################################
+
+certifi==2018.11.29
+chardet==3.0.4
+click==7.0
+coreapi-cli==1.0.9
+coreapi==2.3.3
+coreschema==0.0.4
+dj-database-url==0.5.0
+django-filter==2.0.0
+django-heroku==0.3.1
+django==2.1.4
+djangorestframework==3.9.0
+gunicorn==19.9.0
+httpie==1.0.2
+idna==2.7
+itypes==1.1.0
+jinja2==2.10
+markdown==3.0.1
+markupsafe==1.1.0
+pbr==5.1.1
+pipenv-to-requirements==0.6.1
+pipenv==2018.11.26
+psycopg2==2.7.6.1
+pygments==2.3.0
+pytz==2018.7
+pyyaml==3.13
+requests==2.20.1
+uritemplate==3.0.0
+urllib3==1.24.1
+uwsgi==2.0.17.1
+virtualenv-clone==0.4.0
+virtualenv==16.1.0
+whitenoise==4.1.2

requirements.txt

@@ -0,0 +1,28 @@
+"""WSGI config for project.
+
+This module contains the WSGI application used by Django's development server
+and any production WSGI deployments. It should expose a module-level variable
+named ``application``. Django's ``runserver`` and ``runfcgi`` commands discover
+this application via the ``WSGI_APPLICATION`` setting.
+
+Usually you will have the standard Django WSGI application here, but it also
+might make sense to replace the whole Django WSGI application with a custom one
+that later delegates to the Django one. For example, you could introduce WSGI
+middleware here, or combine a Django application with an application of another
+framework.
+"""
+import os
+os.environ.setdefault('DJANGO_SETTINGS_MODULE', 'apiconfig.settings')
+
+# This application object is used by any WSGI server configured to use this
+# file. This includes Django's development server, if the WSGI_APPLICATION
+# setting points here.
+from django.core.wsgi import get_wsgi_application  # noqa
+application = get_wsgi_application()
+
+# Apply WSGI middleware here.
+# from helloworld.wsgi import HelloWorldApplication
+# application = HelloWorldApplication(application)
+from .health_check import health_check  # noqa
+
+application = health_check(application, '/health/')

wsgi/__init__.py

@@ -0,0 +1,7 @@
+def health_check(application, health_url):
+    def health_check_wrapper(environ, start_response):
+        if environ.get('PATH_INFO') == health_url:
+            start_response('200 OK', [('Content-Type', 'text/plain')])
+            return []
+        return application(environ, start_response)
+    return health_check_wrapper

wsgi/health_check.py

@@ -0,0 +1,10 @@
+[uwsgi]
+die-on-term = true
+http-socket = :$(PORT)
+log-format = UWSGI uwsgi "%(method) %(uri) %(proto)" %(status) %(size) %(msecs)ms [PID:%(pid):Worker-%(wid)] [RSS:%(rssM)MB]
+master = true
+max-requests = 100
+memory-report = true
+module = apiconfig.wsgi:application
+processes = 4
+static-map = /static=/app/static