React-Django react redux base: Seedstars Labs Base Django React Redux Project

Build Status

Django React/Redux Base Project

This repository includes a boilerplate project used for all Seedstars Labs applications. It uses Django as backend and React as frontend.

We build on the shoulders of giants with the following technologies:

Frontend

Backend

  • Django
  • Django REST framework Django REST framework is a powerful and flexible toolkit for building Web APIs
  • Django REST Knox Token based authentication for API endpoints
  • WhiteNoise to serve files efficiently from Django
  • Prospector a complete Python static analysis tool
  • Bandit a security linter from OpenStack Security
  • pytest a mature full-featured Python testing tool
  • Mock mocking and testing Library
  • Responses a utility for mocking out the Python Requests library

Readme Notes

  • If the command line starts with $, the command should run with user privileges
  • If the command line starts with #, the command should run with root privileges

Retrieve code

  • $ git clone https://github.com/seedstars/django-react-redux-base.git
  • $ cd django-react-redux-base
  • $ git submodule init
  • $ git submodule update
  • $ ./scripts/get_static_validation.sh

Remember that when you copy this repository for a new project you need to add the scripts external module using:

  • $ git submodule add https://github.com/Seedstars/culture-scripts scripts

NOTE: This is only needed in case you copy this code to a new project. If you only clone or fork the repository, the submodule is already configured

Installation

You have two ways of running this project: Using the Dockers scripts or running directly in the console.

Running NO DOCKER

NodeJS tooling

  • $ wget -qO- https://deb.nodesource.com/setup_6.x | sudo bash -
  • $ apt-get install --yes nodejs
  • $ curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -
  • $ echo "deb https://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
  • $ sudo apt-get update && sudo apt-get install yarn

Compile and run project

There are commands you need to compile javascript and run project. Ideally yarn run dev should be run in another console because it blocks it.

  • $ yarn

  • $ yarn run dev # will run webpack with watch and compile code as it changes

  • $ virtualenv -p /usr/bin/python3 virtualenv

  • $ source virtualenv/bin/activate

  • $ pip install -r py-requirements/dev.txt

  • $ cd src

  • $ python manage.py migrate

  • $ python manage.py loaddata fixtures.json

  • $ python manage.py runserver

Then open your browser the page: http://localhost:8000/ If all goes ok you should see a React single page app.

Running DOCKER

We use Docker as a development environment. For production, we leave you to set it up the way you feel better, although it is trivial to extrapolate a production environment from the current docker-compose.yml.

To stop the development server:

  • $ docker-compose stop

Stop Docker development server and remove containers, networks, volumes, and images created by up.

  • $ docker-compose down

You can access shell in a container

  • $ docker ps # get the name from the list of running containers
  • $ docker exec -i -t djangoreactreduxbase_frontend_1 /bin/bash

The database can be accessed @localhost:5433

  • $ psql -h localhost -p 5433 -U djangoreactredux djangoreactredux_dev

Accessing Website

The project has CORS enabled and the URL is hard-coded in javascript to http://localhost:8000 For login to work you will to use this URL in your browser.

Testing

To make sure the code respects all coding guidelines you should run the statics analysis and test scripts before pushing any code.

Frontend (javascript tests)

  • $ ./scripts/test_local_frontend.sh

Backend (django/python tests)

  • $ ./scripts/test_local_backend.sh

Please take into account that test_local_backend.sh runs py.test with --nomigrations --reuse-db flags to allow it be performant. Any time you add a migration please remove those flags next time you run the script.

Static analysis

Frontend (javascript static analysis)

  • $ ./scripts/static_validate_frontend.sh

Backend (django/python static analysis)

  • $ ./scripts/static_validate_backend.sh

Deployment in Production

We deploy all our production code using Kubernetes. Explaining how to do deployments is beyond the scope of this boilerplate.

Here's a great article from digital ocean on how to deploy django project in a VM: https://www.digitalocean.com/community/tutorials/how-to-set-up-django-with-postgres-nginx-and-gunicorn-on-ubuntu-16-04

Screenshots

Here are some screenshots of the boilerplate project.

Screenshot01

Screenshot02

Gotchas in Docker

  • This project uses NodeJS v6.x (stable) and yarn
  • The development server takes longer than the django server to start, as it has to install the javascript dependencies (if not already installed) and fire webpack. This means that after the django server starts, you should wait that webpack finishes compiling the .js files.
  • If your IDE has builtin language support for python with auto-imports (e.g. PyCharm), you can create a virtualenv and install the py-requirements.
  • If you are annoyed by docker creating files belonging to root (which is Docker's intended behaviour), you can run # chown -hR $(whoami) . before firing up the server.

Contributing

We welcome contributions from the community, given that they respect these basic guidelines:

  • All Tests & Static Analysis passing;
  • 100% code coverage;

Prior to any pull-request, we advise to open an issue. This is because, although we are happy to merge your code, we must make sure the changes don't impact our way of doing things, thus resulting on a declined PR, and your time wasted.

If you want to tackle any open issue, well..... Just go for it! :)

Comments

  • fix specifying namespace
    fix specifying namespace

    Apr 10, 2019

                                                                                                                                                                                                           
    Reply
  • Upgraded to Django 2.2.1 & DRF 3.9 plus some other package upgrades with minor changes.
    Upgraded to Django 2.2.1 & DRF 3.9 plus some other package upgrades with minor changes.

    Jun 3, 2019

    Fixes #115 & #111. Upgraded almost every package to its latest release and migrated to Django 2.2.1 & DRF 3.9. Changed two incompatible packages that the project was using them:

    django-disposable-email-checker
    

    Which did not support Django 2.2.1, I switched it to email_validator, which almost has the same functionality.

    django-rest-knox==3.0.3
    

    Which was incompatible, I switched it to a more reliable and known package called django-rest-auth and moved to its Token Authentication method.

    Reply
  • Travis CI build fails while running tests for upgraded Django 2.2.1
    Travis CI build fails while running tests for upgraded Django 2.2.1

    Jun 4, 2019

    Fix for #120. Travis CI should be reconfigured. It cannot find djnago==2.2.1 to install it for testing purpose. I think it's because pip version of this current configuration is too old (Version 9 it is I think, which now we have version 19). @lfrodrigues

    Reply
  • Bump jquery from 3.2.1 to 3.5.0
    Bump jquery from 3.2.1 to 3.5.0

    Apr 29, 2020

    Bumps jquery from 3.2.1 to 3.5.0.

    Commits
    • 7a0a850 3.5.0
    • 8570a08 Release: Update AUTHORS.txt
    • da3dd85 Ajax: Do not execute scripts for unsuccessful HTTP responses
    • 065143c Ajax: Overwrite s.contentType with content-type header value, if any
    • 1a4f10d Tests: Blacklist one focusin test in IE
    • 9e15d6b Event: Use only one focusin/out handler per matching window & document
    • 966a709 Manipulation: Skip the select wrapper for <option> outside of IE 9
    • 1d61fd9 Manipulation: Make jQuery.htmlPrefilter an identity function
    • 04bf577 Selector: Update Sizzle from 2.3.4 to 2.3.5
    • 7506c9c Build: Resolve Travis config warnings
    • Additional commits viewable in compare view
    Maintainer changes

    This version was pushed to npm by mgol, a new releaser for jquery since your current version.


    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies javascript 
    Reply
  • Adding TypeScript support
    Adding TypeScript support

    May 15, 2020

    Is integrating TypeScript support into webpack on the roadmap at all?

    Would this require a refactor of src/static?

    Reply
  • Error running Docker-componse build
    Error running Docker-componse build

    Jul 14, 2020

    When I run docker-compose build I get the following error (note that python and setuptools are the latest version on the device):

    Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-w44kketk/pytest-xdist/ You are using pip version 9.0.1, however version 20.1.1 is available. You should consider upgrading via the 'pip install --upgrade pip' command. ERROR: Service 'backend' failed to build: The command '/bin/sh -c pip install -r py-requirements/dev.txt' returned a non-zero code: 1

    docker-compose build
    nginx uses an image, skipping
    Building postgres
    Step 1/3 : FROM postgres:9.5.4
     ---> 2417ea518abc
    Step 2/3 : ENV POSTGRES_USER postgres
     ---> Using cache
     ---> f64ceabf4cef
    Step 3/3 : WORKDIR /
     ---> Using cache
     ---> 3c1f40ecff5e
    Successfully built 3c1f40ecff5e
    Successfully tagged django-react-redux-base_postgres:latest
    Building backend
    Step 1/8 : FROM python:3.4.3
     ---> 2b07576f6f81
    Step 2/8 : MAINTAINER Filipe Garcia <[email protected]>
     ---> Using cache
     ---> 29a8f748dccf
    Step 3/8 : ENV PYTHONUNBUFFERED 1
     ---> Using cache
     ---> 6d3ec7f9181e
    Step 4/8 : COPY ./docker/django/django-entrypoint.sh /
     ---> Using cache
     ---> bb91df46e91c
    Step 5/8 : COPY ./py-requirements /django/py-requirements
     ---> Using cache
     ---> 6d1d1bc41483
    Step 6/8 : WORKDIR /django
     ---> Using cache
     ---> 526ae3d75196
    Step 7/8 : RUN pip install pip==9.0.1
     ---> Using cache
     ---> dd48ca4e6cc6
    Step 8/8 : RUN pip install -r py-requirements/dev.txt
     ---> Running in 8538b4a6b436
    Collecting git+https://github.com/Seedstars/django-rest-logger.git (from -r py-requirements/base.txt (line 22))
      Cloning https://github.com/Seedstars/django-rest-logger.git to /tmp/pip-uxzzll16-build
    Collecting Django==1.11.4 (from -r py-requirements/base.txt (line 1))
      Downloading https://files.pythonhosted.org/packages/fc/fb/01e0084061c50f1160c2db5565ff1c3d8d76f2a76f67cd282835ee64e04a/Django-1.11.4-py2.py3-none-any.whl (6.9MB)
    Collecting django-extensions==1.8.1 (from -r py-requirements/base.txt (line 2))
      Downloading https://files.pythonhosted.org/packages/5f/aa/ec44557aae10616963d96be967caf6a1615fe3a4d3400666073c29640f4c/django_extensions-1.8.1-py2.py3-none-any.whl (204kB)
    Collecting django-disposable-email-checker==1.2.1 (from -r py-requirements/base.txt (line 4))
      Downloading https://files.pythonhosted.org/packages/3f/9b/d7ef5f1dd983a4a610b4097a8092010ef95dbf8a3fe780277dfd6c308994/django_disposable_email_checker-1.2.1-py2.py3-none-any.whl
    Collecting psycopg2==2.7.3 (from -r py-requirements/base.txt (line 7))
      Downloading https://files.pythonhosted.org/packages/93/54/78d05449901047b300de1fda9a964411cc48456839038a716f673bededd9/psycopg2-2.7.3-cp34-cp34m-manylinux1_x86_64.whl (2.7MB)
    Collecting whitenoise==3.3.0 (from -r py-requirements/base.txt (line 10))
      Downloading https://files.pythonhosted.org/packages/86/b4/1aedb1ed7561087ba9f93592ef398cfd4ed7551503ae9f305311d0b6ed84/whitenoise-3.3.0-py2.py3-none-any.whl
    Collecting djangorestframework==3.6.4 (from -r py-requirements/base.txt (line 13))
      Downloading https://files.pythonhosted.org/packages/12/22/98d2ea3089384b88f1ed86fb2799d8c57b59ce430c3972ec0f18986cd449/djangorestframework-3.6.4-py2.py3-none-any.whl (1.5MB)
    Collecting raven==6.1.0 (from -r py-requirements/base.txt (line 16))
      Downloading https://files.pythonhosted.org/packages/17/c0/c78198b9f2459f28de1bcba7a3586602a5b85858e9657db59e881fbea89f/raven-6.1.0-py2.py3-none-any.whl (279kB)
    Collecting python-dateutil==2.6.1 (from -r py-requirements/base.txt (line 19))
      Downloading https://files.pythonhosted.org/packages/4b/0d/7ed381ab4fe80b8ebf34411d14f253e1cf3e56e2820ffa1d8844b23859a2/python_dateutil-2.6.1-py2.py3-none-any.whl (194kB)
    Collecting django-rest-knox==3.0.3 (from -r py-requirements/base.txt (line 24))
      Downloading https://files.pythonhosted.org/packages/84/e9/e60f25d317ce4d6c249e76251c60eaa5f7b246d67ae9a8ec9db49de3de80/django_rest_knox-3.0.3-py3-none-any.whl
    Collecting mock==2.0.0 (from -r py-requirements/dev.txt (line 3))
      Downloading https://files.pythonhosted.org/packages/e6/35/f187bdf23be87092bd0f1200d43d23076cee4d0dec109f195173fd3ebc79/mock-2.0.0-py2.py3-none-any.whl (56kB)
    Collecting factory-boy==2.9.2 (from -r py-requirements/dev.txt (line 4))
      Downloading https://files.pythonhosted.org/packages/81/b9/ca160fdcfd7313d59151aa60a2d2125d5677f4147a2c7e14a3736560e271/factory_boy-2.9.2-py2.py3-none-any.whl
    Collecting prospector==0.12.7 (from -r py-requirements/dev.txt (line 6))
      Downloading https://files.pythonhosted.org/packages/f3/66/1b500570209f10c4dc8491e93505c8a52ca06953e25c7881159df3af6604/prospector-0.12.7.tar.gz (52kB)
    Collecting bandit==1.4.0 (from -r py-requirements/dev.txt (line 7))
      Downloading https://files.pythonhosted.org/packages/77/41/d57366098a30a86af1821e231949221d2b6b896cc4bdd060cc1be27fdd47/bandit-1.4.0-py2.py3-none-any.whl (116kB)
    Collecting pytest==3.2.1 (from -r py-requirements/dev.txt (line 9))
      Downloading https://files.pythonhosted.org/packages/e0/1e/d52c6a3a143935410ee33320341ea7bbb770ca8fe89c3d51e18254e0a2ba/pytest-3.2.1-py2.py3-none-any.whl (186kB)
    Collecting pytest-cov==2.5.1 (from -r py-requirements/dev.txt (line 10))
      Downloading https://files.pythonhosted.org/packages/30/7d/7f6a78ae44a1248ee28cc777586c18b28a1df903470e5d34a6e25712b8aa/pytest_cov-2.5.1-py2.py3-none-any.whl
    Collecting pytest-django==3.1.2 (from -r py-requirements/dev.txt (line 11))
      Downloading https://files.pythonhosted.org/packages/0f/c4/123ec7829e175af511c5be0501df9552261c2bf549b8e7a43ba35505594e/pytest_django-3.1.2-py2.py3-none-any.whl
    Collecting pytest-pythonpath==0.7.1 (from -r py-requirements/dev.txt (line 12))
      Downloading https://files.pythonhosted.org/packages/ad/28/c0068d0bbdec562bacbe1de866138ae10241cc0b7eba7c4b8a2ac8d4474d/pytest-pythonpath-0.7.1.tar.gz
    Collecting pytest-xdist==1.20.0 (from -r py-requirements/dev.txt (line 13))
      Downloading https://files.pythonhosted.org/packages/16/52/a76faa9f4ecede7dc9cc08177b65a90ed377136445edbb3f1a969b223ef5/pytest-xdist-1.20.0.tar.gz (56kB)
        Complete output from command python setup.py egg_info:
        /usr/local/lib/python3.4/site-packages/pkg_resources/__init__.py:2510: PEP440Warning: 'setuptools (scm-1.0.0)' is being parsed as a legacy, non PEP 440, version. You may find odd behavior and sort order. In particular it will be sorted as less than 0.0. It is recommend to migrate to PEP 440 compatible versions.
          PEP440Warning,
        /usr/local/lib/python3.4/site-packages/pkg_resources/__init__.py:2510: PEP440Warning: 'setuptools (scm-1.1.0)' is being parsed as a legacy, non PEP 440, version. You may find odd behavior and sort order. In particular it will be sorted as less than 0.0. It is recommend to migrate to PEP 440 compatible versions.
          PEP440Warning,
        /usr/local/lib/python3.4/site-packages/pkg_resources/__init__.py:2510: PEP440Warning: 'setuptools (scm-1.2.0)' is being parsed as a legacy, non PEP 440, version. You may find odd behavior and sort order. In particular it will be sorted as less than 0.0. It is recommend to migrate to PEP 440 compatible versions.
          PEP440Warning,
        /usr/local/lib/python3.4/site-packages/pkg_resources/__init__.py:2510: PEP440Warning: 'setuptools (scm-1.3.0)' is being parsed as a legacy, non PEP 440, version. You may find odd behavior and sort order. In particular it will be sorted as less than 0.0. It is recommend to migrate to PEP 440 compatible versions.
          PEP440Warning,
        /usr/local/lib/python3.4/site-packages/pkg_resources/__init__.py:2510: PEP440Warning: 'setuptools (scm-1.4.0)' is being parsed as a legacy, non PEP 440, version. You may find odd behavior and sort order. In particular it will be sorted as less than 0.0. It is recommend to migrate to PEP 440 compatible versions.
          PEP440Warning,
        /tmp/easy_install-6b0oxhiq/setuptools_scm-4.1.2/src
        <pkg_resources.WorkingSet object at 0x7f8022e646d8>
        warning: no previously-included files found matching '*.nix'
        warning: no previously-included files found matching '.travis.yaml'
        warning: no previously-included files found matching '.pre-commit-config.yaml'
        warning: install_lib: 'build/lib' does not exist -- no Python modules to install
    
        zip_safe flag not set; analyzing archive contents...
    
        Installed /tmp/pip-build-co4am_uy/pytest-xdist/.eggs/UNKNOWN-4.1.2-py3.4.egg
        Traceback (most recent call last):
          File "<string>", line 1, in <module>
          File "/tmp/pip-build-co4am_uy/pytest-xdist/setup.py", line 44, in <module>
            'Programming Language :: Python :: 3',
          File "/usr/local/lib/python3.4/distutils/core.py", line 108, in setup
            _setup_distribution = dist = klass(attrs)
          File "/usr/local/lib/python3.4/site-packages/setuptools/dist.py", line 265, in __init__
            self.fetch_build_eggs(attrs['setup_requires'])
          File "/usr/local/lib/python3.4/site-packages/setuptools/dist.py", line 311, in fetch_build_eggs
            replace_conflicting=True,
          File "/usr/local/lib/python3.4/site-packages/pkg_resources/__init__.py", line 805, in resolve
            raise DistributionNotFound(req)
        pkg_resources.DistributionNotFound: setuptools-scm
        ----------------------------------------
    Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-co4am_uy/pytest-xdist/
    You are using pip version 9.0.1, however version 20.1.1 is available.
    You should consider upgrading via the 'pip install --upgrade pip' command.
    ERROR: Service 'backend' failed to build: The command '/bin/sh -c pip install -r py-requirements/dev.txt' returned a non-zero code: 1        
    PS C:\Users\bob\Documents\GitHub\django-react-redux-base> docker-compose build
    nginx uses an image, skipping
    Building postgres
    Step 1/3 : FROM postgres:9.5.4
     ---> 2417ea518abc
    Step 2/3 : ENV POSTGRES_USER postgres
     ---> Using cache
     ---> f64ceabf4cef
    Step 3/3 : WORKDIR /
     ---> Using cache
     ---> 3c1f40ecff5e
    Successfully built 3c1f40ecff5e
    Successfully tagged django-react-redux-base_postgres:latest
    Building backend
    Step 1/8 : FROM python:3.4.3
     ---> 2b07576f6f81
    Step 2/8 : MAINTAINER Filipe Garcia <[email protected]>
     ---> Using cache
     ---> 29a8f748dccf
    Step 3/8 : ENV PYTHONUNBUFFERED 1
     ---> Using cache
     ---> 6d3ec7f9181e
    Step 4/8 : COPY ./docker/django/django-entrypoint.sh /
     ---> Using cache
     ---> bb91df46e91c
    Step 5/8 : COPY ./py-requirements /django/py-requirements
     ---> a48a0997bf3a
    Step 6/8 : WORKDIR /django
     ---> Running in 70aa2afeb511
    Removing intermediate container 70aa2afeb511
     ---> 8e3f81bd7612
    Step 7/8 : RUN pip install pip==9.0.1
     ---> Running in e8587b827acc
    Collecting pip==9.0.1
      Downloading https://files.pythonhosted.org/packages/b6/ac/7015eb97dc749283ffdec1c3a88ddb8ae03b8fad0f0e611408f196358da3/pip-9.0.1-py2.py3-none-any.whl (1.3MB)
    Installing collected packages: pip
      Found existing installation: pip 7.1.2
        Uninstalling pip-7.1.2:
          Successfully uninstalled pip-7.1.2
    Successfully installed pip-9.0.1
    You are using pip version 9.0.1, however version 20.1.1 is available.
    You should consider upgrading via the 'pip install --upgrade pip' command.
    Removing intermediate container e8587b827acc
     ---> 40e577002d5a
    Step 8/8 : RUN pip install -r py-requirements/dev.txt
     ---> Running in 09fabdbd1c29
    Collecting git+https://github.com/Seedstars/django-rest-logger.git (from -r py-requirements/base.txt (line 22))
      Cloning https://github.com/Seedstars/django-rest-logger.git to /tmp/pip-ddp7ywqq-build
    Collecting Django==1.11.29 (from -r py-requirements/base.txt (line 1))
      Downloading https://files.pythonhosted.org/packages/49/49/178daa8725d29c475216259eb19e90b2aa0b8c0431af8c7e9b490ae6481d/Django-1.11.29-py2.py3-none-any.whl (6.9MB)
    Collecting django-extensions==1.8.1 (from -r py-requirements/base.txt (line 2))
      Downloading https://files.pythonhosted.org/packages/5f/aa/ec44557aae10616963d96be967caf6a1615fe3a4d3400666073c29640f4c/django_extensions-1.8.1-py2.py3-none-any.whl (204kB)
    Collecting django-disposable-email-checker==1.2.1 (from -r py-requirements/base.txt (line 4))
      Downloading https://files.pythonhosted.org/packages/3f/9b/d7ef5f1dd983a4a610b4097a8092010ef95dbf8a3fe780277dfd6c308994/django_disposable_email_checker-1.2.1-py2.py3-none-any.whl
    Collecting psycopg2==2.7.3 (from -r py-requirements/base.txt (line 7))
      Downloading https://files.pythonhosted.org/packages/93/54/78d05449901047b300de1fda9a964411cc48456839038a716f673bededd9/psycopg2-2.7.3-cp34-cp34m-manylinux1_x86_64.whl (2.7MB)
    Collecting whitenoise==3.3.0 (from -r py-requirements/base.txt (line 10))
      Downloading https://files.pythonhosted.org/packages/86/b4/1aedb1ed7561087ba9f93592ef398cfd4ed7551503ae9f305311d0b6ed84/whitenoise-3.3.0-py2.py3-none-any.whl
    Collecting djangorestframework==3.6.4 (from -r py-requirements/base.txt (line 13))
      Downloading https://files.pythonhosted.org/packages/12/22/98d2ea3089384b88f1ed86fb2799d8c57b59ce430c3972ec0f18986cd449/djangorestframework-3.6.4-py2.py3-none-any.whl (1.5MB)
    Collecting raven==6.1.0 (from -r py-requirements/base.txt (line 16))
      Downloading https://files.pythonhosted.org/packages/17/c0/c78198b9f2459f28de1bcba7a3586602a5b85858e9657db59e881fbea89f/raven-6.1.0-py2.py3-none-any.whl (279kB)
    Collecting python-dateutil==2.6.1 (from -r py-requirements/base.txt (line 19))
      Downloading https://files.pythonhosted.org/packages/4b/0d/7ed381ab4fe80b8ebf34411d14f253e1cf3e56e2820ffa1d8844b23859a2/python_dateutil-2.6.1-py2.py3-none-any.whl (194kB)
    Collecting django-rest-knox==3.0.3 (from -r py-requirements/base.txt (line 24))
      Downloading https://files.pythonhosted.org/packages/84/e9/e60f25d317ce4d6c249e76251c60eaa5f7b246d67ae9a8ec9db49de3de80/django_rest_knox-3.0.3-py3-none-any.whl
    Collecting mock==2.0.0 (from -r py-requirements/dev.txt (line 3))
      Downloading https://files.pythonhosted.org/packages/e6/35/f187bdf23be87092bd0f1200d43d23076cee4d0dec109f195173fd3ebc79/mock-2.0.0-py2.py3-none-any.whl (56kB)
    Collecting factory-boy==2.9.2 (from -r py-requirements/dev.txt (line 4))
      Downloading https://files.pythonhosted.org/packages/81/b9/ca160fdcfd7313d59151aa60a2d2125d5677f4147a2c7e14a3736560e271/factory_boy-2.9.2-py2.py3-none-any.whl
    Collecting prospector==0.12.7 (from -r py-requirements/dev.txt (line 6))
      Downloading https://files.pythonhosted.org/packages/f3/66/1b500570209f10c4dc8491e93505c8a52ca06953e25c7881159df3af6604/prospector-0.12.7.tar.gz (52kB)
    Collecting bandit==1.4.0 (from -r py-requirements/dev.txt (line 7))
      Downloading https://files.pythonhosted.org/packages/77/41/d57366098a30a86af1821e231949221d2b6b896cc4bdd060cc1be27fdd47/bandit-1.4.0-py2.py3-none-any.whl (116kB)
    Collecting pytest==3.2.1 (from -r py-requirements/dev.txt (line 9))
      Downloading https://files.pythonhosted.org/packages/e0/1e/d52c6a3a143935410ee33320341ea7bbb770ca8fe89c3d51e18254e0a2ba/pytest-3.2.1-py2.py3-none-any.whl (186kB)
    Collecting pytest-cov==2.5.1 (from -r py-requirements/dev.txt (line 10))
      Downloading https://files.pythonhosted.org/packages/30/7d/7f6a78ae44a1248ee28cc777586c18b28a1df903470e5d34a6e25712b8aa/pytest_cov-2.5.1-py2.py3-none-any.whl
    Collecting pytest-django==3.1.2 (from -r py-requirements/dev.txt (line 11))
      Downloading https://files.pythonhosted.org/packages/0f/c4/123ec7829e175af511c5be0501df9552261c2bf549b8e7a43ba35505594e/pytest_django-3.1.2-py2.py3-none-any.whl
    Collecting pytest-pythonpath==0.7.1 (from -r py-requirements/dev.txt (line 12))
      Downloading https://files.pythonhosted.org/packages/ad/28/c0068d0bbdec562bacbe1de866138ae10241cc0b7eba7c4b8a2ac8d4474d/pytest-pythonpath-0.7.1.tar.gz
    Collecting pytest-xdist==1.20.0 (from -r py-requirements/dev.txt (line 13))
      Downloading https://files.pythonhosted.org/packages/16/52/a76faa9f4ecede7dc9cc08177b65a90ed377136445edbb3f1a969b223ef5/pytest-xdist-1.20.0.tar.gz (56kB)
        Complete output from command python setup.py egg_info:
        /usr/local/lib/python3.4/site-packages/pkg_resources/__init__.py:2510: PEP440Warning: 'setuptools (scm-1.0.0)' is being parsed as a legacy, non PEP 440, version. You may find odd behavior and sort order. In particular it will be sorted as less than 0.0. It is recommend to migrate to PEP 440 compatible versions.
          PEP440Warning,
        /usr/local/lib/python3.4/site-packages/pkg_resources/__init__.py:2510: PEP440Warning: 'setuptools (scm-1.1.0)' is being parsed as a legacy, non PEP 440, version. You may find odd behavior and sort order. In particular it will be sorted as less than 0.0. It is recommend to migrate to PEP 440 compatible versions.
          PEP440Warning,
        /usr/local/lib/python3.4/site-packages/pkg_resources/__init__.py:2510: PEP440Warning: 'setuptools (scm-1.2.0)' is being parsed as a legacy, non PEP 440, version. You may find odd behavior and sort order. In particular it will be sorted as less than 0.0. It is recommend to migrate to PEP 440 compatible versions.
          PEP440Warning,
        /usr/local/lib/python3.4/site-packages/pkg_resources/__init__.py:2510: PEP440Warning: 'setuptools (scm-1.3.0)' is being parsed as a legacy, non PEP 440, version. You may find odd behavior and sort order. In particular it will be sorted as less than 0.0. It is recommend to migrate to PEP 440 compatible versions.
          PEP440Warning,
        /usr/local/lib/python3.4/site-packages/pkg_resources/__init__.py:2510: PEP440Warning: 'setuptools (scm-1.4.0)' is being parsed as a legacy, non PEP 440, version. You may find odd behavior and sort order. In particular it will be sorted as less than 0.0. It is recommend to migrate to PEP 440 compatible versions.
          PEP440Warning,
        /tmp/easy_install-l97mcius/setuptools_scm-4.1.2/src
        <pkg_resources.WorkingSet object at 0x7f1d087ce748>
        warning: no previously-included files found matching '*.nix'
        warning: no previously-included files found matching '.travis.yaml'
        warning: no previously-included files found matching '.pre-commit-config.yaml'
        warning: install_lib: 'build/lib' does not exist -- no Python modules to install
    
        zip_safe flag not set; analyzing archive contents...
    
        Installed /tmp/pip-build-w44kketk/pytest-xdist/.eggs/UNKNOWN-4.1.2-py3.4.egg
        Traceback (most recent call last):
          File "<string>", line 1, in <module>
          File "/tmp/pip-build-w44kketk/pytest-xdist/setup.py", line 44, in <module>
          File "/usr/local/lib/python3.4/distutils/core.py", line 108, in setup
            _setup_distribution = dist = klass(attrs)
          File "/usr/local/lib/python3.4/site-packages/setuptools/dist.py", line 265, in __init__
            self.fetch_build_eggs(attrs['setup_requires'])
          File "/usr/local/lib/python3.4/site-packages/setuptools/dist.py", line 311, in fetch_build_eggs
            replace_conflicting=True,
          File "/usr/local/lib/python3.4/site-packages/pkg_resources/__init__.py", line 805, in resolve
            raise DistributionNotFound(req)
        pkg_resources.DistributionNotFound: setuptools-scm
    
        ----------------------------------------
    Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-w44kketk/pytest-xdist/
    You are using pip version 9.0.1, however version 20.1.1 is available.
    You should consider upgrading via the 'pip install --upgrade pip' command.
    ERROR: Service 'backend' failed to build: The command '/bin/sh -c pip install -r py-requirements/dev.txt' returned a non-zero code: 1    
    
    Reply
  • Bump node-sass from 4.5.3 to 4.14.1
    Bump node-sass from 4.5.3 to 4.14.1

    Sep 3, 2020

    Bumps node-sass from 4.5.3 to 4.14.1.

    Release notes

    Sourced from node-sass's releases.

    v4.14.1

    Community

    Fixes

    Supported Environments

    OS Architecture Node
    Windows x86 & x64 0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14
    OSX x64 0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14
    Linux* x86 & x64 0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8**, 9**, 10**^, 11**^, 12**^, 13**^, 14**^
    Alpine Linux x64 6, 8, 10, 11, 12, 13, 14
    FreeBSD i386 amd64 10, 12, 13

    *Linux support refers to Ubuntu, Debian, and CentOS 5+ ** Not available on CentOS 5 ^ Only available on x64

    v4.14.0

    Features

    Fixes

    Supported Environments

    OS Architecture Node
    Windows x86 & x64 0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14
    OSX x64 0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14
    Linux* x86 & x64 0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8**, 9**, 10**^, 11**^, 12**^, 13**^, 14**^
    Alpine Linux x64 6, 8, 10, 11, 12, 13, 14
    FreeBSD i386 amd64 10, 12, 13

    *Linux support refers to Ubuntu, Debian, and CentOS 5+ ** Not available on CentOS 5 ^ Only available on x64

    v4.13.1

    Community

    Changelog

    Sourced from node-sass's changelog.

    v4.14.0

    https://github.com/sass/node-sass/releases/tag/v4.14.0

    v4.13.1

    https://github.com/sass/node-sass/releases/tag/v4.13.1

    v4.13.0

    https://github.com/sass/node-sass/releases/tag/v4.13.0

    v4.12.0

    https://github.com/sass/node-sass/releases/tag/v4.12.0

    v4.11.0

    https://github.com/sass/node-sass/releases/tag/v4.11.0

    v4.10.0

    https://github.com/sass/node-sass/releases/tag/v4.10.0

    v4.9.4

    https://github.com/sass/node-sass/releases/tag/v4.9.4

    v4.9.3

    https://github.com/sass/node-sass/releases/tag/v4.9.3

    v4.9.2

    https://github.com/sass/node-sass/releases/tag/v4.9.2

    v4.9.1

    https://github.com/sass/node-sass/releases/tag/v4.9.1

    v4.9.0

    https://github.com/sass/node-sass/releases/tag/v4.9.0

    v4.8.3

    https://github.com/sass/node-sass/releases/tag/v4.8.3

    v4.8.2

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies javascript 
    Reply
  • Bump djangorestframework from 3.6.4 to 3.11.2 in /py-requirements
    Bump djangorestframework from 3.6.4 to 3.11.2 in /py-requirements

    Mar 19, 2021

    Bumps djangorestframework from 3.6.4 to 3.11.2.

    Release notes

    Sourced from djangorestframework's releases.

    Version 3.9.3

    This is the last Django REST Framework release that will support Python 2. Be sure to upgrade to Python 3 before upgrading to Django REST Framework 3.10.

    • Adjusted the compat check for django-guardian to allow the last guardian version (v1.4.9) compatible with Python 2. #6613

    Version 3.9.2

    See Release Notes for details.

    Version 3.9.1

    Change Notes: https://www.django-rest-framework.org/community/release-notes/#39x-series

    Verision 3.9.0

    Release announcement: https://www.django-rest-framework.org/community/3.9-announcement/

    Change Notes: https://www.django-rest-framework.org/community/release-notes/#39x-series

    Version 3.8.2

    Point release for 3.8.x series

    • Fix read_only + default unique_together validation. #5922
    • authtoken.views import coreapi from rest_framework.compat, not directly. #5921
    • Docs: Add missing argument 'detail' to Route #5920

    Version 3.8.1

    • Use old url_name behavior in route decorators #5915

      For list_route and detail_route maintain the old behavior of url_name, basing it on the url_path instead of the function name.

    Version 3.8

    • Release Announcement

    • 3.8.0 Milestone

    • Breaking Change: Alter read_only plus default behaviour. #5886

      read_only fields will now always be excluded from writable fields.

      Previously read_only fields with a default value would use the default for create and update operations.

      In order to maintain the old behaviour you may need to pass the value of read_only fields when calling save() in the view:

        def perform_create(self, serializer):
            serializer.save(owner=self.request.user)
      

    ... (truncated)

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies python 
    Reply
  • Add gitpod configs
    Add gitpod configs

    Mar 23, 2021

                                                                                                                                                                                                           
    Reply
  • Bump django from 1.11.4 to 2.2.24 in /py-requirements
    Bump django from 1.11.4 to 2.2.24 in /py-requirements

    Jun 10, 2021

    Bumps django from 1.11.4 to 2.2.24.

    Commits
    • 2da029d [2.2.x] Bumped version for 2.2.24 release.
    • f27c38a [2.2.x] Fixed CVE-2021-33571 -- Prevented leading zeros in IPv4 addresses.
    • 053cc95 [2.2.x] Fixed CVE-2021-33203 -- Fixed potential path-traversal via admindocs'...
    • 6229d87 [2.2.x] Confirmed release date for Django 2.2.24.
    • f163ad5 [2.2.x] Added stub release notes and date for Django 2.2.24.
    • bed1755 [2.2.x] Changed IRC references to Libera.Chat.
    • 63f0d7a [2.2.x] Refs #32718 -- Fixed file_storage.test_generate_filename and model_fi...
    • 5fe4970 [2.2.x] Post-release version bump.
    • 61f814f [2.2.x] Bumped version for 2.2.23 release.
    • b8ecb06 [2.2.x] Fixed #32718 -- Relaxed file name validation in FileField.
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies python 
    Reply
  • css order with CommonsChunkPlugin
    css order with CommonsChunkPlugin

    May 12, 2017

    How i can change order of load output css files with CommonsChunkPlugin?

    Now vendor load after app. it is override app css with vendors css selectors.

    Reply
  • Postgres errors on docker-compose up
    Postgres errors on docker-compose up

    Jun 9, 2017

    I just did a fresh clone of this, and am running into some issues related to postgres.

    When I do the initial "docker-compose build", I get this output:

    postgres uses an image, skipping
    Building backend
    Step 1/8 : FROM python:3.4.3
     ---> 2b07576f6f81
    Step 2/8 : MAINTAINER Filipe Garcia <[email protected]>
     ---> Using cache
     ---> 296027a66659
    Step 3/8 : ENV PYTHONUNBUFFERED 1
     ---> Using cache
     ---> fed44573bddd
    Step 4/8 : COPY ./docker/django/django-entrypoint.sh /
     ---> Using cache
     ---> b69db680c93d
    Step 5/8 : COPY ./py-requirements /django/py-requirements
     ---> Using cache
     ---> 576d3405234d
    Step 6/8 : WORKDIR /django
     ---> Using cache
     ---> 02c221c59ece
    Step 7/8 : RUN pip install pip==9.0.1
     ---> Using cache
     ---> 9c91b226a552
    Step 8/8 : RUN pip install -r py-requirements/dev.txt
     ---> Using cache
     ---> bfc22d48cb00
    Successfully built bfc22d48cb00
    Building frontend
    Step 1/10 : FROM ubuntu:14.04
     ---> 132b7427a3b4
    Step 2/10 : MAINTAINER Filipe Garcia <[email protected]>
     ---> Using cache
     ---> 00d86baf1030
    Step 3/10 : COPY ./docker/web/web-entrypoint.sh /
     ---> Using cache
     ---> a62b34c6bd7c
    Step 4/10 : COPY ./package.json /django/package.json
     ---> Using cache
     ---> 36ee5f392448
    Step 5/10 : WORKDIR /django
     ---> Using cache
     ---> 734314b9aafa
    Step 6/10 : RUN apt-get update && apt-get install -y curl
     ---> Using cache
     ---> ce490bd17798
    Step 7/10 : RUN curl -sL https://deb.nodesource.com/setup_6.x | sudo -E bash -
     ---> Using cache
     ---> 39b89bdbe154
    Step 8/10 : RUN curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -
     ---> Using cache
     ---> 1cf467cea39d
    Step 9/10 : RUN echo "deb http://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
     ---> Using cache
     ---> 02c0fbe67d4e
    Step 10/10 : RUN apt-get update && apt-get install -y nodejs yarn
     ---> Using cache
     ---> f7ed3d16a205
    Successfully built f7ed3d16a205
    nginx uses an image, skipping
    

    I'm not sure if the docker and nginx "skipping" comments are problematic or working-as-intended, but the following "docker-compose up" command results in the following. I'm not sure if there was some kind of install step I missed beforehand, or any version requirements I'm missing.

    Starting charitytriage_postgres_1
    Starting charitytriage_backend_1
    Starting charitytriage_nginx_1
    Starting charitytriage_frontend_1
    Attaching to charitytriage_postgres_1, charitytriage_backend_1, charitytriage_nginx_1, charitytriage_frontend_1
    postgres_1  | LOG:  database system was interrupted; last known up at 2017-06-10 00:11:53 UTC
    postgres_1  | LOG:  database system was not properly shut down; automatic recovery in progress
    postgres_1  | LOG:  invalid record length at 0/1000198
    postgres_1  | LOG:  redo is not required
    backend_1   | Traceback (most recent call last):
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/base/base.py", line 130, in ensure_connection
    postgres_1  | LOG:  MultiXact member wraparound protections are now enabled
    backend_1   |     self.connect()
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/base/base.py", line 119, in connect
    postgres_1  | LOG:  database system is ready to accept connections
    backend_1   |     self.connection = self.get_new_connection(conn_params)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/postgresql_psycopg2/base.py", line 176, in get_new_connection
    backend_1   |     connection = Database.connect(**conn_params)
    postgres_1  | LOG:  autovacuum launcher started
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/psycopg2/__init__.py", line 164, in connect
    backend_1   |     conn = _connect(dsn, connection_factory=connection_factory, async=async)
    backend_1   | psycopg2.OperationalError: FATAL:  no pg_hba.conf entry for host "172.18.0.3", user "djangoreactredux", database "djangoreactredux_dev", SSL off
    backend_1   |
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    backend_1   |
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    backend_1   | The above exception was the direct cause of the following exception:
    backend_1   |
    backend_1   | Traceback (most recent call last):
    backend_1   |   File "manage.py", line 10, in <module>
    backend_1   |     execute_from_command_line(sys.argv)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/core/management/__init__.py", line 354, in execute_from_command_line
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    backend_1   |     utility.execute()
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/core/management/__init__.py", line 346, in execute
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    backend_1   |     self.fetch_command(subcommand).run_from_argv(self.argv)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/core/management/base.py", line 394, in run_from_argv
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    backend_1   |     self.execute(*args, **cmd_options)
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/core/management/base.py", line 445, in execute
    backend_1   |     output = self.handle(*args, **options)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/core/management/commands/migrate.py", line 93, in handle
    backend_1   |     executor = MigrationExecutor(connection, self.migration_progress_callback)
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/migrations/executor.py", line 19, in __init__
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    backend_1   |     self.loader = MigrationLoader(self.connection)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/migrations/loader.py", line 47, in __init__
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    backend_1   |     self.build_graph()
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/migrations/loader.py", line 191, in build_graph
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    backend_1   |     self.applied_migrations = recorder.applied_migrations()
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/migrations/recorder.py", line 59, in applied_migrations
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    backend_1   |     self.ensure_schema()
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/migrations/recorder.py", line 49, in ensure_schema
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    backend_1   |     if self.Migration._meta.db_table in self.connection.introspection.table_names(self.connection.cursor()):
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/base/base.py", line 162, in cursor
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    backend_1   |     cursor = self.make_debug_cursor(self._cursor())
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/base/base.py", line 135, in _cursor
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    backend_1   |     self.ensure_connection()
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/base/base.py", line 130, in ensure_connection
    backend_1   |     self.connect()
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/utils.py", line 98, in __exit__
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    backend_1   |     six.reraise(dj_exc_type, dj_exc_value, traceback)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/utils/six.py", line 685, in reraise
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    backend_1   |     raise value.with_traceback(tb)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/base/base.py", line 130, in ensure_connection
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    backend_1   |     self.connect()
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/base/base.py", line 119, in connect
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    backend_1   |     self.connection = self.get_new_connection(conn_params)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/postgresql_psycopg2/base.py", line 176, in get_new_connection
    backend_1   |     connection = Database.connect(**conn_params)
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/psycopg2/__init__.py", line 164, in connect
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    backend_1   |     conn = _connect(dsn, connection_factory=connection_factory, async=async)
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    backend_1   | django.db.utils.OperationalError: FATAL:  no pg_hba.conf entry for host "172.18.0.3", user "djangoreactredux", database "djangoreactredux_dev", SSL off
    backend_1   |
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    backend_1   | Waiting for postgres ready...
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  "base/1" is not a valid data directory
    postgres_1  | DETAIL:  File "base/1/PG_VERSION" is missing.
    postgres_1  | FATAL:  no pg_hba.conf entry for host "172.18.0.3", user "djangoreactredux", database "djangoreactredux_dev", SSL off
    frontend_1  | yarn install v0.24.6
    frontend_1  | [1/4] Resolving packages...
    frontend_1  | success Already up-to-date.
    frontend_1  | Done in 0.83s.
    frontend_1  |
    frontend_1  | > [email protected] dev /django
    frontend_1  | > webpack --progress --display-error-details --config webpack/common.config.js --watch
    frontend_1  |
    postgres_1  | FATAL:  no pg_hba.conf entry for host "172.18.0.3", user "djangoreactredux", database "djangoreactredux_dev", SSL off
    backend_1   | Traceback (most recent call last):
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/base/base.py", line 130, in ensure_connection
    backend_1   |     self.connect()
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/base/base.py", line 119, in connect
    backend_1   |     self.connection = self.get_new_connection(conn_params)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/postgresql_psycopg2/base.py", line 176, in get_new_connection
    backend_1   |     connection = Database.connect(**conn_params)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/psycopg2/__init__.py", line 164, in connect
    backend_1   |     conn = _connect(dsn, connection_factory=connection_factory, async=async)
    backend_1   | psycopg2.OperationalError: FATAL:  no pg_hba.conf entry for host "172.18.0.3", user "djangoreactredux", database "djangoreactredux_dev", SSL off
    backend_1   |
    backend_1   |
    backend_1   | The above exception was the direct cause of the following exception:
    backend_1   |
    backend_1   | Traceback (most recent call last):
    backend_1   |   File "manage.py", line 10, in <module>
    backend_1   |     execute_from_command_line(sys.argv)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/core/management/__init__.py", line 354, in execute_from_command_line
    backend_1   |     utility.execute()
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/core/management/__init__.py", line 346, in execute
    backend_1   |     self.fetch_command(subcommand).run_from_argv(self.argv)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/core/management/base.py", line 394, in run_from_argv
    backend_1   |     self.execute(*args, **cmd_options)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/core/management/base.py", line 445, in execute
    backend_1   |     output = self.handle(*args, **options)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/core/management/commands/migrate.py", line 93, in handle
    backend_1   |     executor = MigrationExecutor(connection, self.migration_progress_callback)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/migrations/executor.py", line 19, in __init__
    backend_1   |     self.loader = MigrationLoader(self.connection)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/migrations/loader.py", line 47, in __init__
    backend_1   |     self.build_graph()
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/migrations/loader.py", line 191, in build_graph
    backend_1   |     self.applied_migrations = recorder.applied_migrations()
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/migrations/recorder.py", line 59, in applied_migrations
    backend_1   |     self.ensure_schema()
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/migrations/recorder.py", line 49, in ensure_schema
    backend_1   |     if self.Migration._meta.db_table in self.connection.introspection.table_names(self.connection.cursor()):
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/base/base.py", line 162, in cursor
    backend_1   |     cursor = self.make_debug_cursor(self._cursor())
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/base/base.py", line 135, in _cursor
    backend_1   |     self.ensure_connection()
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/base/base.py", line 130, in ensure_connection
    backend_1   |     self.connect()
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/utils.py", line 98, in __exit__
    backend_1   |     six.reraise(dj_exc_type, dj_exc_value, traceback)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/utils/six.py", line 685, in reraise
    backend_1   |     raise value.with_traceback(tb)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/base/base.py", line 130, in ensure_connection
    backend_1   |     self.connect()
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/base/base.py", line 119, in connect
    backend_1   |     self.connection = self.get_new_connection(conn_params)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/postgresql_psycopg2/base.py", line 176, in get_new_connection
    backend_1   |     connection = Database.connect(**conn_params)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/psycopg2/__init__.py", line 164, in connect
    backend_1   |     conn = _connect(dsn, connection_factory=connection_factory, async=async)
    backend_1   | django.db.utils.OperationalError: FATAL:  no pg_hba.conf entry for host "172.18.0.3", user "djangoreactredux", database "djangoreactredux_dev", SSL off
    backend_1   |
    backend_1   | Waiting for postgres ready...
    frontend_1  | clean-webpack-plugin: /django/src/static_dist has been removed.
    frontend_1  |  10% building modules 1/1 modules 0 active
    frontend_1  | Webpack is watching the files…
    frontend_1  |
    postgres_1  | FATAL:  no pg_hba.conf entry for host "172.18.0.3", user "djangoreactredux", database "djangoreactredux_dev", SSL off
    backend_1   | Traceback (most recent call last):
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/base/base.py", line 130, in ensure_connection
    backend_1   |     self.connect()
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/base/base.py", line 119, in connect
    backend_1   |     self.connection = self.get_new_connection(conn_params)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/postgresql_psycopg2/base.py", line 176, in get_new_connection
    backend_1   |     connection = Database.connect(**conn_params)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/psycopg2/__init__.py", line 164, in connect
    backend_1   |     conn = _connect(dsn, connection_factory=connection_factory, async=async)
    backend_1   | psycopg2.OperationalError: FATAL:  no pg_hba.conf entry for host "172.18.0.3", user "djangoreactredux", database "djangoreactredux_dev", SSL off
    backend_1   |
    backend_1   |
    backend_1   | The above exception was the direct cause of the following exception:
    backend_1   |
    backend_1   | Traceback (most recent call last):
    backend_1   |   File "manage.py", line 10, in <module>
    backend_1   |     execute_from_command_line(sys.argv)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/core/management/__init__.py", line 354, in execute_from_command_line
    backend_1   |     utility.execute()
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/core/management/__init__.py", line 346, in execute
    backend_1   |     self.fetch_command(subcommand).run_from_argv(self.argv)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/core/management/base.py", line 394, in run_from_argv
    backend_1   |     self.execute(*args, **cmd_options)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/core/management/base.py", line 445, in execute
    backend_1   |     output = self.handle(*args, **options)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/core/management/commands/migrate.py", line 93, in handle
    backend_1   |     executor = MigrationExecutor(connection, self.migration_progress_callback)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/migrations/executor.py", line 19, in __init__
    backend_1   |     self.loader = MigrationLoader(self.connection)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/migrations/loader.py", line 47, in __init__
    backend_1   |     self.build_graph()
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/migrations/loader.py", line 191, in build_graph
    backend_1   |     self.applied_migrations = recorder.applied_migrations()
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/migrations/recorder.py", line 59, in applied_migrations
    backend_1   |     self.ensure_schema()
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/migrations/recorder.py", line 49, in ensure_schema
    backend_1   |     if self.Migration._meta.db_table in self.connection.introspection.table_names(self.connection.cursor()):
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/base/base.py", line 162, in cursor
    backend_1   |     cursor = self.make_debug_cursor(self._cursor())
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/base/base.py", line 135, in _cursor
    backend_1   |     self.ensure_connection()
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/base/base.py", line 130, in ensure_connection
    backend_1   |     self.connect()
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/utils.py", line 98, in __exit__
    backend_1   |     six.reraise(dj_exc_type, dj_exc_value, traceback)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/utils/six.py", line 685, in reraise
    backend_1   |     raise value.with_traceback(tb)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/base/base.py", line 130, in ensure_connection
    backend_1   |     self.connect()
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/base/base.py", line 119, in connect
    backend_1   |     self.connection = self.get_new_connection(conn_params)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/postgresql_psycopg2/base.py", line 176, in get_new_connection
    backend_1   |     connection = Database.connect(**conn_params)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/psycopg2/__init__.py", line 164, in connect
    backend_1   |     conn = _connect(dsn, connection_factory=connection_factory, async=async)
    backend_1   | django.db.utils.OperationalError: FATAL:  no pg_hba.conf entry for host "172.18.0.3", user "djangoreactredux", database "djangoreactredux_dev", SSL off
    backend_1   |
    backend_1   | Waiting for postgres ready...
    postgres_1  | FATAL:  no pg_hba.conf entry for host "172.18.0.3", user "djangoreactredux", database "djangoreactredux_dev", SSL off
    backend_1   | Traceback (most recent call last):
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/base/base.py", line 130, in ensure_connection
    backend_1   |     self.connect()
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/base/base.py", line 119, in connect
    backend_1   |     self.connection = self.get_new_connection(conn_params)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/postgresql_psycopg2/base.py", line 176, in get_new_connection
    backend_1   |     connection = Database.connect(**conn_params)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/psycopg2/__init__.py", line 164, in connect
    backend_1   |     conn = _connect(dsn, connection_factory=connection_factory, async=async)
    backend_1   | psycopg2.OperationalError: FATAL:  no pg_hba.conf entry for host "172.18.0.3", user "djangoreactredux", database "djangoreactredux_dev", SSL off
    backend_1   |
    backend_1   |
    backend_1   | The above exception was the direct cause of the following exception:
    backend_1   |
    backend_1   | Traceback (most recent call last):
    backend_1   |   File "manage.py", line 10, in <module>
    backend_1   |     execute_from_command_line(sys.argv)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/core/management/__init__.py", line 354, in execute_from_command_line
    backend_1   |     utility.execute()
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/core/management/__init__.py", line 346, in execute
    backend_1   |     self.fetch_command(subcommand).run_from_argv(self.argv)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/core/management/base.py", line 394, in run_from_argv
    backend_1   |     self.execute(*args, **cmd_options)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/core/management/base.py", line 445, in execute
    backend_1   |     output = self.handle(*args, **options)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/core/management/commands/migrate.py", line 93, in handle
    backend_1   |     executor = MigrationExecutor(connection, self.migration_progress_callback)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/migrations/executor.py", line 19, in __init__
    backend_1   |     self.loader = MigrationLoader(self.connection)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/migrations/loader.py", line 47, in __init__
    backend_1   |     self.build_graph()
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/migrations/loader.py", line 191, in build_graph
    backend_1   |     self.applied_migrations = recorder.applied_migrations()
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/migrations/recorder.py", line 59, in applied_migrations
    backend_1   |     self.ensure_schema()
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/migrations/recorder.py", line 49, in ensure_schema
    backend_1   |     if self.Migration._meta.db_table in self.connection.introspection.table_names(self.connection.cursor()):
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/base/base.py", line 162, in cursor
    backend_1   |     cursor = self.make_debug_cursor(self._cursor())
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/base/base.py", line 135, in _cursor
    backend_1   |     self.ensure_connection()
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/base/base.py", line 130, in ensure_connection
    backend_1   |     self.connect()
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/utils.py", line 98, in __exit__
    backend_1   |     six.reraise(dj_exc_type, dj_exc_value, traceback)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/utils/six.py", line 685, in reraise
    backend_1   |     raise value.with_traceback(tb)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/base/base.py", line 130, in ensure_connection
    backend_1   |     self.connect()
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/base/base.py", line 119, in connect
    backend_1   |     self.connection = self.get_new_connection(conn_params)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/django/db/backends/postgresql_psycopg2/base.py", line 176, in get_new_connection
    backend_1   |     connection = Database.connect(**conn_params)
    backend_1   |   File "/usr/local/lib/python3.4/site-packages/psycopg2/__init__.py", line 164, in connect
    backend_1   |     conn = _connect(dsn, connection_factory=connection_factory, async=async)
    backend_1   | django.db.utils.OperationalError: FATAL:  no pg_hba.conf entry for host "172.18.0.3", user "djangoreactredux", database "djangoreactredux_dev", SSL off
    backend_1   |
    backend_1   | Waiting for postgres ready...
    
    Reply
  • HELP - How to deploy this to AWS EC2?
    HELP - How to deploy this to AWS EC2?

    Jun 4, 2017

                                                                                                                                                                                                           
    Reply
  • `npm run coverage` error.
    `npm run coverage` error.

    May 9, 2016

    Hello, when I run npm run coverage, I got a error:

    ➜  django-react-redux-jwt-base git:(master) ✗ npm run coverage         
    
    > [email protected] coverage /opt/django-react-redux-jwt-base
    > istanbul cover node_modules/mocha/bin/_mocha -- --require tests/require --recursive --compilers js:babel-core/register --colors --reporter dot tests/js/
    
    Warning: `valueLink` prop on `input` is deprecated; set `value` and `onChange` instead.
    
    
      ․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․
    
      58 passing (341ms)
    
    Unable to post-instrument: /opt/django-react-redux-jwt-base/src/static/containers/index.js
    Unable to post-instrument: /opt/django-react-redux-jwt-base/src/static/containers/Root/DevTools.js
    Unable to post-instrument: /opt/django-react-redux-jwt-base/src/static/containers/Root/Root.dev.js
    Unable to post-instrument: /opt/django-react-redux-jwt-base/src/static/containers/Root/Root.prod.js
    Unable to post-instrument: /opt/django-react-redux-jwt-base/src/static/index.js
    Unable to post-instrument: /opt/django-react-redux-jwt-base/src/static/reducers/index.js
    Unable to post-instrument: /opt/django-react-redux-jwt-base/src/static/routes.js
    Unable to post-instrument: /opt/django-react-redux-jwt-base/src/static/store/configureStore.dev.js
    Unable to post-instrument: /opt/django-react-redux-jwt-base/src/static/store/configureStore.prod.js
    Unable to post-instrument: /opt/django-react-redux-jwt-base/src/static/utils/requireAuthentication.js
    /opt/django-react-redux-jwt-base/node_modules/.npminstall/istanbul-api/1.0.0-aplha.1/istanbul-api/lib/reporter.js:80
            reportSource = libReport.createReportSource(coverageMap, opts);
                                     ^
    
    TypeError: libReport.createReportSource is not a function
        at Object.Reporter.write (/opt/django-react-redux-jwt-base/node_modules/.npminstall/istanbul-api/1.0.0-aplha.1/istanbul-api/lib/reporter.js:80:34)
        at exitFn (/opt/django-react-redux-jwt-base/node_modules/.npminstall/istanbul-api/1.0.0-aplha.1/istanbul-api/lib/run-cover.js:127:18)
        at process.g (events.js:273:16)
        at emitOne (events.js:95:20)
        at process.emit (events.js:182:7)
        at process.exit (internal/process.js:79:15)
        at done (/opt/django-react-redux-jwt-base/node_modules/.npminstall/mocha/2.4.5/mocha/bin/_mocha:416:32)
        at afterWrite (_stream_writable.js:355:3)
        at _combinedTickCallback (internal/process/next_tick.js:80:20)
        at process._tickCallback (internal/process/next_tick.js:98:9)
    
    
    npm ERR! Darwin 15.3.0
    npm ERR! argv "/Users/yie/.nvm/versions/node/v5.10.1/bin/node" "/Users/yie/.nvm/versions/node/v5.10.1/bin/npm" "run" "coverage"
    npm ERR! node v5.10.1
    npm ERR! npm  v3.8.3
    npm ERR! code ELIFECYCLE
    npm ERR! [email protected] coverage: `istanbul cover node_modules/mocha/bin/_mocha -- --require tests/require --recursive --compilers js:babel-core/register --colors --reporter dot tests/js/`
    npm ERR! Exit status 1
    npm ERR! 
    npm ERR! Failed at the [email protected] coverage script 'istanbul cover node_modules/mocha/bin/_mocha -- --require tests/require --recursive --compilers js:babel-core/register --colors --reporter dot tests/js/'.
    npm ERR! Make sure you have the latest version of node.js and npm installed.
    npm ERR! If you do, this is most likely a problem with the django-react-redux-jwt-base package,
    npm ERR! not with npm itself.
    npm ERR! Tell the author that this fails on your system:
    npm ERR!     istanbul cover node_modules/mocha/bin/_mocha -- --require tests/require --recursive --compilers js:babel-core/register --colors --reporter dot tests/js/
    npm ERR! You can get information on how to open an issue for this project with:
    npm ERR!     npm bugs django-react-redux-jwt-base
    npm ERR! Or if that isn't available, you can get their info via:
    npm ERR!     npm owner ls django-react-redux-jwt-base
    
    Reply
  • Build Error with Yarn
    Build Error with Yarn

    Sep 4, 2017

    I'm getting a build error with the Yarn package manager. It's in regards to babel. This is the error I'm getting:

    BabelLoaderError: SyntaxError: Unexpected token (17:4)
    
      15 | 
      16 | const node = (
    > 17 |     <Root store={store} history={history} />
         |     ^
      18 | );
      19 | 
      20 | const token = sessionStorage.getItem('token');
    
    

    By all logic, this react code should work right? I'm on Ubuntu 16.04 and all other parts of the build work. Cannot confirm if you all get the same error. Fails to build in docker too.

    Reply
  • Uncaught SyntaxError: Unexpected token <
    Uncaught SyntaxError: Unexpected token <

    Sep 15, 2017

    I frequently get this error after running "yarn run dev" and running the server.

    This is the only error output : app.b8da97e0aa7de58fcb04.js:1 Uncaught SyntaxError: Unexpected token < vendor.b8da97e0aa7de58fcb04.js:1 Uncaught SyntaxError: Unexpected token <

    However sometimes it works when I ran "yarn run dev", not sure what im missing or why this occurs sometimes?

    Reply
  • Include django-allauth or django-rest w/ django-allauth ?
    Include django-allauth or django-rest w/ django-allauth ?

    Dec 27, 2016

                                                                                                                                                                                                           
    Reply
  • Error with Docker on Windows
    Error with Docker on Windows

    Jun 21, 2017

    I am trying to run the app using Docker on Windows 10, but I am getting the following error:

    No such file or directoryuxbase_backend_1 | /usr/bin/env: bash

    Docker version is:

    Client:
     Version:      17.03.1-ce
     API version:  1.27
     Go version:   go1.7.5
     Git commit:   c6d412e
     Built:        Tue Mar 28 00:40:02 2017
     OS/Arch:      windows/amd64
    
    Server:
     Version:      17.03.1-ce
     API version:  1.27 (minimum version 1.12)
     Go version:   go1.7.5
     Git commit:   c6d412e
     Built:        Fri Mar 24 00:00:50 2017
     OS/Arch:      linux/amd64
     Experimental: true
    

    I tried to convert the scripts with unix2dos, just in case, but it did not work.

    Reply
  • Postgres not persisting data to shared volumes between runs
    Postgres not persisting data to shared volumes between runs

    Jan 18, 2017

    I'm currently running the app and populating postgres with data. I see there is a volumes entry in docker-common.yml, and assumed data would be persisted between container runs to './docker/postgres/data', but have not seen data get persisted.

    Assistance on this would be greatly appreciated as I've been banging my head against my keyboard all day but still can't figure it out.

    volumes: - ./docker/postgres/data:/var/lib/postgresql

    question 
    Reply
  • Deployment Documentation
    Deployment Documentation

    Apr 27, 2017

    I think it would be good if it had a brief/in-depth documentation on the deployment.

    Reply