seedstars / django-react-redux-base Goto Github PK

View Code? Open in Web Editor NEW

2.7K 2.7K 342.0 741 KB

Seedstars Labs Base Django React Redux Project

License: MIT License

Python 31.32% Shell 0.57% JavaScript 64.50% CSS 2.74% HTML 0.19% Dockerfile 0.69%

django react redux

django-react-redux-base's People

Contributors

Stargazers

Watchers

Forkers

zixan nunb sharpertool noscripter tiansiyuan jdgoren abossard gauthamses rmoorman daniel1943 vickyonit romansemko codinronan shamigor rturowicz andrealmar davidgillies sotebob kajarenc drjackild fthzkrtn sinyawskiy andrealmieda ieiayaobb felsen jknightihiji mayblue9 bbeckrest dtraviglia ithacadream fmoggia bernardojedi darrindickey evgenyboxer szwork2013 moyuan aadu chuan137 uhjish pconerly volkandkaya terrykfwong igravious mikebarile amjd liondancer edevil sboselli pombredanne yanlinaung sughodke beacoding mrsmartpants bonsaikitt3n fsnlarson xiaowli haykbaluyan dmreiland frankbie caraclarke kureck kustomzone gisairo skynode eternonq guinslym rasouli hustshawn dilansri setevik fortunado bbuneci xinyuanyu smoll lmchawla smbrero tbikeev briangrace johnsonc skylifewww vanpitkinobi naruto2902git mouli6 jenlesamuel gerbyzation rodnandes artocully sangkilee fivethreeo mstbbs arihrannar yianlai tonggee mbuffenoir yetanothertimes american-desi jjwill devnard andrewglancy jbaek7023

django-react-redux-base's Issues

Update to new webpack

Update build to use new webpack 2 (has breaking changes)

Are there plans to support server side rendering of react components

Accessing Django admin

Hi,

Sorry if it's a silly question- but I cannot access the traditional Django Admin site. has it been removed?

Thanks

I'm usually for minimal boilerplates, but with how well it works with Redux, Immutable.js has become an automatic "every project" add for my team. Anyone that's not using it with Redux is missing out, IMO!

Of course, I understand keeping the boilerplate as minimal as possible and just asking users to make their own decision as well.

When do you plan to include React Router v4?

Why I cannot fetch login interface

I followed the steps in the README.md,
However, when I visit 'http://localhost:8000/api/v1/accounts/login/', I only get message as "non_field_errors": [
"Method "GET" not allowed."
]

anybody who can help me solve this? thank you

Support for gettext internationalization in the frontend?

https://blog.sentry.io/2016/01/07/react-i18n.html

Remove window.INITIAL_STATE

Since we are not rendering anything server side, this variable is redundant, and is set to undefined in beginning.

Error installing fixture

When the backend service spins up, it errors out as follows:

django.core.serializers.base.DeserializationError: Problem installing fixture '/django/src/fixtures.json': User has no field named 'username'

This looks to prevent the default user from being added which prevents me from logging in to the protected area.

Is there any plan to reduce the bundle size?

The default webpack production config will produce 5M+ bundle.js(vendor.js), it is bad idea to serve the index to such a cost, do you guys have the plan to reduce the bundle size or split them into smaller chunks?

Deployment Documentation

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

No 'Access-Control-Allow-Origin' header is present on the requested resource.

I had this error on Google Chrome (similar on firefox) when following readme:

Fetch API cannot load http://localhost:8000/api/v1/accounts/login/. Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://127.0.0.1:8000' is therefore not allowed access. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

I had to install django-cors-middleware and append these lines to djangoreactredux.settings.dev to be able to make it work:

INSTALLED_APPS += ('corsheaders',)

MIDDLEWARE_CLASSES += (
    'corsheaders.middleware.CorsMiddleware',
    )

CORS_ORIGIN_ALLOW_ALL = True
CORS_ALLOW_CREDENTIALS = True

Since I don't have much experience with git, maybe someone wants to make a PR.

*Loved the example by the way!

how to get app up and running (out of box?)

Hi, I'm pretty new to this django and docker setup - what steps should i run to get the boiler site up and running out of the box?

login does not work

Hi,

I've just installed this great boilerplate (thanks a lot by the way).
Unfortunatly, when I try to login, I have the following error message: "Authentication Error: Connection Error - An error occurred while sending your data!"

Looking at the API requests, I see that an OPTIONS method is sent before POST can be executed (CORS preflight?) and Django responds with "OPTIONS /api/v1/accounts/login/ HTTP/1.0" 401 70

Do you have any idea how I could fix this problem?

Thanks!

[Feature Request] : Post CSS anyone?

I'm working on a post css inclusion with gulp build system. Anyone?
Suggestions?

pip install requirements

virtualenv • ~/p/django-react-redux-jwt-base $ pip install -r py-requirements/dev.txt

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 /var/folders/td/f_yq56sx30v7gw7yrryk556r0000gn/T/pip-m0o2kw84-build
Collecting Django==1.8.15 (from -r py-requirements/base.txt (line 1))
  Downloading Django-1.8.15-py2.py3-none-any.whl (6.2MB)
    100% |████████████████████████████████| 6.2MB 238kB/s
Collecting django-extensions==1.7.4 (from -r py-requirements/base.txt (line 2))
  Downloading django_extensions-1.7.4-py2.py3-none-any.whl (200kB)
    100% |████████████████████████████████| 204kB 2.3MB/s
Collecting django-disposable-email-checker==1.2.1 (from -r py-requirements/base.txt (line 4))
  Downloading django_disposable_email_checker-1.2.1-py2.py3-none-any.whl
Collecting psycopg2==2.6.2 (from -r py-requirements/base.txt (line 7))
  Downloading psycopg2-2.6.2.tar.gz (376kB)
    100% |████████████████████████████████| 378kB 1.8MB/s
    Complete output from command python setup.py egg_info:
    running egg_info
    creating pip-egg-info/psycopg2.egg-info
    writing top-level names to pip-egg-info/psycopg2.egg-info/top_level.txt
    writing dependency_links to pip-egg-info/psycopg2.egg-info/dependency_links.txt
    writing pip-egg-info/psycopg2.egg-info/PKG-INFO
    writing manifest file 'pip-egg-info/psycopg2.egg-info/SOURCES.txt'
    warning: manifest_maker: standard file '-c' not found

    Error: pg_config executable not found.

    Please add the directory containing pg_config to the PATH
    or specify the full executable path with the option:

        python setup.py build_ext --pg-config /path/to/pg_config build ...

    or with the pg_config option in 'setup.cfg'.

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /private/var/folders/td/f_yq56sx30v7gw7yrryk556r0000gn/T/pip-build-kx_qtjqi/psycopg2/

NOTE: Last line is in red.

virtualenv • ~/p/django-react-redux-jwt-base $ uname -a

Darwin My-MacBook-Pro.local 16.1.0 Darwin Kernel Version 16.1.0: Thu Oct 13 21:26:57 PDT 2016; root:xnu-3789.21.3~60/RELEASE_X86_64 x86_64

Serializer class should not be a tuple in APIView

In the Account views, the serializer class is denoted as empty tuple(Line 54 and 73). It should either be a proper serilizer class or None.

Here

ERR_CONNECTION_REFUSED

If an ERR_CONNECTION_REFUSEDhappen when trying to login, no message are display to the user.

Use redux saga instead of thunk?

https://github.com/yelouafi/redux-saga

Why use arrays as object keys in your reducer?

Hi,

Thanks for making this project. It's been a good learning experience for me to read through it.

However, I've been reading your reducer code and I've been scratching my head a little bit. Why use arrays as object keys in your reducers?

export default createReducer(initialState, {
    [AUTH_LOGIN_USER_REQUEST]: (state, payload) => {
        return Object.assign({}, state, {
            isAuthenticating: true,
            statusText: null
        });
    },
    ...

Is there some benefit to doing this that I don't understand?

Thanks!

P.S. Wouldn't it be better for createReducer() to raise an error when it can't find the right reducer? Right now, it'll silently fail and return the initial state.

Hot Reloading?

Thanks for the great boilerplate!
Do you have any plans to include react-hot-loader?

CSS not loading on production

I deployed this app on ec2, if i use dev settings, all working well.But when i am using production settings, css is not loading.I am getting this error, "Resource interpreted as Stylesheet but transferred with MIME type text/html:"
"Uncaught SyntaxError: "

`server {
listen 80;
server_name 13.xx.xx.xxx;

location = /favicon.ico { access_log off; log_not_found off; }
location /static_dist/ {
    root /home/ubuntu/studykarma/django-react-redux-base/src;
}
location / {
    include proxy_params;
    include  /etc/nginx/mime.types;
    proxy_pass http://unix:/home/ubuntu/studykarma/django-react-redux-base/src/djangoreactredux.sock;
}

}`
This is my nginx config file

username field

username field has unique = true option but hasn't been included in the fields of UserRegisterSerializer

Include travis CI

window.INITIAL_STATE is undefined

I've taken the repo and integrated Typescript with the React app, but in building the application I get an error that window.INITIAL_STATE is undefined. Is this by design?

If I had to guess, Typescript is failing here because it is never defined, whereas lazy ol Javascript would just take it and roll, and configure store would just get undefined as initial state.

I think that's it, but can someone confirm/deny?

Accessing the built-in Django admin area?

Thanks for this awesome boilerplate guys!

I have been able to set up the majority of it and things are working fine.

However, when I go to /admin, the response is NOT FOUND.

Because the routing is being handled by React/Redux now, am I not able to use the built-in Django admin functionality/features?

Error in dependencies wrt webpack

I get the following errors on dependencies after webpack was upgraded to webpack 2.2.0rc1:
npm WARN [email protected] requires a peer of webpack@^2.1.0-beta but none was installed.
npm WARN [email protected] requires a peer of webpack@^2.1.0-beta.19 but none was installed.
npm WARN [email protected] requires a peer of webpack@1 || ^2.1.0-beta but none was installed.
npm WARN [email protected] requires a peer of webpack@^1.12.6 || ^2.1.0-beta but none was installed.

Where and why do we use jQuery?

Thank you for this project, guys!

I think it's overkill to use jQuery with React. Do we really need it?

Sending Email

First of all Thanks for this boilerplate.

I have some issue about registration.
when i am registration a new user how can I send activation email and activate the user.
Thanks

frontend exited with code 0

Firstly, thanks for providing this boilerplate. It's far more advanced and feature rich than others out there.

I have been trying to set this up on my windows laptop (using Docker Quickstart Terminal) and after overcoming some small obstacles I have found myself stuck.

The postgres, backend and nginx containers all attach well but the frontend is failing with error code 0 (no error).

On npm run dev, it seems to die while unpacking the modules and it always terminates at the same place [6].

I tried:

--bail option on the webpack command but it didnt show an error.
I thought it could be reaching a memory limit so i removed glyphicons but it died at the same line.
tty: true in the frontend docker service with COMPOSE_HTTP_TIMEOUT=200

Since there is no error I have little to work with to troubleshoot.

Here is the relevant output of docker-compose --verbose up

frontend_1  | Version: webpack 2.2.1
frontend_1  | Time: 29652ms
frontend_1  |                                                   Asset       Size
  Chunks                    Chunk Names
frontend_1  | /images/react-logo.png?bf6e7aa4366ba93442e42038897d683d    35.1 kB          [emitted]
frontend_1  |                          /fonts/fontawesome-webfont.eot     166 kB          [emitted]
frontend_1  |                        /fonts/fontawesome-webfont.woff2    77.2 kB          [emitted]
frontend_1  |                          /fonts/fontawesome-webfont.ttf     166 kB          [emitted]
frontend_1  |                          /fonts/fontawesome-webfont.svg     444 kB          [emitted]  [big]
frontend_1  |                 /fonts/glyphicons-halflings-regular.eot    20.1 kB          [emitted]
frontend_1  |                /fonts/glyphicons-halflings-regular.woff    23.4 kB          [emitted]
frontend_1  |               /fonts/glyphicons-halflings-regular.woff2      18 kB          [emitted]
frontend_1  |                 /fonts/glyphicons-halflings-regular.ttf    45.4 kB          [emitted]
frontend_1  |                 /fonts/glyphicons-halflings-regular.svg     109 kB          [emitted]
frontend_1  |                         /fonts/fontawesome-webfont.woff      98 kB          [emitted]
frontend_1  | /images/redux-logo.png?59c467536111a981d904a050d335c2be     218 kB          [emitted]
frontend_1  |                             app.252ce4abfaa646c2822c.js    1.63 MB       0  [emitted]  [big]  app
frontend_1  |                          vendor.252ce4abfaa646c2822c.js    1.59 MB       1  [emitted]  [big]  vendor
frontend_1  |                                       styles/vendor.css     183 kB       1  [emitted]         vendor
frontend_1  |                                          styles/app.css    2.57 kB       0  [emitted]         app
frontend_1  |                         app.252ce4abfaa646c2822c.js.map       2 MB       0  [emitted]         app
frontend_1  |                                      styles/app.css.map   91 bytes       0  [emitted]         app
frontend_1  |                      vendor.252ce4abfaa646c2822c.js.map    1.97 MB       1  [emitted]         vendor
frontend_1  |                                   styles/vendor.css.map   94 bytes       1  [emitted]         vendor
frontend_1  |                                              index.html  603 bytes          [emitted]
frontend_1  |    [3] /django/~/react/react.js 56 bytes {0} {1} [built]
frontend_1  |   [36] /django/~/classnames/index.js 1.1 kB {0} {1} [built]
...
frontend_1  |        [5] /django/~/bootstrap-sass/assets/fonts/bootstrap/glyphicons-halflings-regular.svg 85 bytes {0} [built]
frontend_1  |        [6] /django/~/css-loader!/django/~/resolve-url-loader!/django/~/sass-loader?sourceMap!/django/~/bootstrap-loader/lib/bootstrap.styles.loader.js?{"bootstrapVersion":3,"useCustomIconFontPath":false,"extractStyles":true,"styleLoaders":["style-loader","css-loader","sass-loader"],"styles":["mixins","normalize","print","glyphicons","scaffolding","type","code","grid","tables","forms","buttons","component-animations","dropdowns","button-groups","input-groups","navs","navbar","breadcrumbs","pagination","pager","labels","badges","jumbotron","thumbnails","alerts","progress-bars","media","list-group","panels","wells","responsive-embed","close","modals","tooltip","popovers","carousel","utilities","responsive-utilities"],"scripts":["transition","alert","button","carousel","collapse","dropdown","modal","tooltip","popover","scrollspy","tab","affix"],"configFilePath":"/django/.bootstraprc","bootstrapPath":"/django/~/bootstrap-sass","bootstrapRelPath":"../bootstrap-sass"}!/django/~/bootstrap-loader/no-op.js 158 kB {0} [built]

djangoreactreduxbase_frontend_1 exited with code 0

pycharm support

I've been trying to start django-react-redux-base with pycharm, but seems pycharm starts containers with no all scripts (i had some template files errors, as i can see - pycham does not run .sh entrypoint files) .
Did anybody has been test it?

example docker compose in pycharm:
https://blog.jetbrains.com/pycharm/2017/03/docker-compose-getting-flask-up-and-running/

ps. pycharm 2016
pps. it works if start
$docker-compose up -- here is all scripts run correctly and create static files and etc...
than terminate it,
and than start debug/run from pycharm

Docker build failing

Doing a docker build on the following repo as defined in the readme file is giving and error

docker-compose build
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
 ---> fb8c1164eb76
Step 3/8 : ENV PYTHONUNBUFFERED 1
 ---> Using cache
 ---> cac86ae2aca7
Step 4/8 : COPY ./docker/django/django-entrypoint.sh /
 ---> Using cache
 ---> e92f5fac5331
Step 5/8 : COPY ./py-requirements /django/py-requirements
 ---> Using cache
 ---> 141951255c71
Step 6/8 : WORKDIR /django
 ---> Using cache
 ---> df57582f5732
Step 7/8 : RUN pip install pip==9.0.1
 ---> Running in eb127faba904
Collecting pip==9.0.1
  Retrying (Retry(total=4, connect=None, read=None, redirect=None)) after connection broken by 'ProtocolError('Connection aborted.', gaierror(-2, 'Name or service not known'))': /simple/pip/
  Retrying (Retry(total=3, connect=None, read=None, redirect=None)) after connection broken by 'ProtocolError('Connection aborted.', gaierror(-2, 'Name or service not known'))': /simple/pip/

Can you please look into the readme file and update it accordingly

Shall we use djangorestframework-jwt for token based authentication ?

Instead of django-rest-knox can we use JSON Web Token Authentication (djangorestframework-jwt)?

/django/src/static_dist/index.html doesn't exist

Followed instructions up to docker-compose up and running localhost:8000 gives /django/src/static_dist/index.html doesn't exist

.eslinrc

Hey,
that is one of the best boilerplates that I had a chance to look into. Thank you very much for it!

I think that can be quite problematic - time taking thing to create by yourself the .eslintrc file with all the rules you use. In previus version the file was included.

Second thing - it's not a tivial thing to find a way of livereload of this project under dev. For me that sholud be included to the base. For the easiest way was to use webpack-livereload-plugin but still I wonder if it's possible to have a hot reload of that project without another server running.

Thank you one more time for this repo

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

Authentication works using sessionStorage

If you set the token using

sessionStorage.setItem('token', 'blahblah')

It works fine and you can access the protected content. Could there be something wrong?

Error with Docker on Windows

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.

Frontend auth is out of sync with backend?

After logging in from the frontend, i cant access the user via self.context.get('request') in the Serializer model, says user doesnt exist. But when I login via the django admin, the user exists. Not sure whats happening :S

I've created a new repo that includes server rendering

Please check it out
https://github.com/ruffers9/django-react-boilerplate

Series of errors on clean install

Thanks for a great project! I would like to offer some comments/experiences when starting from scratch.
I started from scratch on a mac and installed everything according to instructions. I got a number of issues:

--edited issues (added numbering)--

References in README are not updated to djangoreactreduxjwtbase_* (add jwt)
The scripts submodule has already been added in the repository, so README is not correct in the need to add culture-scripts
I had an older version of npm that confused me for a while. It would be useful to document minimum npm version
When running frontend tests, I get an error 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/'
See npm-debug.log.txt
When starting the containers (using Docker for Mac), everything seems to start ok, but when accessing http://localhost:8000/, I get a File not found and several modules (font-awesome etc) not found in the console log. Then I need to wait 55 seconds(!), refresh my browser and then it works
Finally, when running the backend tests, I get several 'The fake-factory package is now called Faker errors.

Starting djangoreactreduxjwtbase_postgres_1
Starting djangoreactreduxjwtbase_backend_1
Starting djangoreactreduxjwtbase_nginx_1
Starting djangoreactreduxjwtbase_frontend_1
Attaching to djangoreactreduxjwtbase_postgres_1, djangoreactreduxjwtbase_backend_1, djangoreactreduxjwtbase_frontend_1, djangoreactreduxjwtbase_nginx_1
postgres_1  | LOG:  database system was shut down at 2016-12-17 08:25:22 UTC
postgres_1  | LOG:  MultiXact member wraparound protections are now enabled
backend_1   | Operations to perform:
backend_1   |   Synchronize unmigrated apps: staticfiles, rest_framework, accounts, django_extensions, base
postgres_1  | LOG:  database system is ready to accept connections
backend_1   |   Apply all migrations: knox, auth, contenttypes
backend_1   | Synchronizing apps without migrations:
backend_1   |   Creating tables...
postgres_1  | LOG:  autovacuum launcher started
backend_1   |     Running deferred SQL...
backend_1   |   Installing custom SQL...
backend_1   | Running migrations:
backend_1   |   No migrations to apply.
frontend_1  | yarn install v0.17.10
frontend_1  | [1/4] Resolving packages...
backend_1   | Installed 1 object(s) from 1 fixture(s)
frontend_1  | success Already up-to-date.
frontend_1  | Done in 0.66s.
frontend_1  | 
frontend_1  | > [email protected] dev /django
frontend_1  | > webpack --progress --display-error-details --config webpack/common.config.js --watch
frontend_1  | 
backend_1   | Performing system checks...
backend_1   | 
backend_1   | System check identified no issues (0 silenced).
backend_1   | December 17, 2016 - 08:25:58
backend_1   | Django version 1.8.15, using settings 'djangoreactredux.settings.dev'
backend_1   | Starting development server at http://0.0.0.0:8000/
backend_1   | Quit the server with CONTROL-C.
frontend_1  | clean-webpack-plugin: /django/src/static_dist has been removed.
backend_1   | [17/Dec/2016 08:26:06] "GET / HTTP/1.0" 500 83907
nginx_1     | 172.18.0.1 - - [17/Dec/2016:08:26:06 +0000] "GET / HTTP/1.1" 500 84015 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.21 Safari/537.36" "-"
nginx_1     | 172.18.0.1 - - [17/Dec/2016:08:26:07 +0000] "GET /favicon.ico HTTP/1.1" 500 83668 "http://localhost:8000/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.21 Safari/537.36" "-"
backend_1   | [17/Dec/2016 08:26:07] "GET /favicon.ico HTTP/1.0" 500 83568
backend_1   | [17/Dec/2016 08:26:13] "GET / HTTP/1.0" 500 83293
nginx_1     | 172.18.0.1 - - [17/Dec/2016:08:26:13 +0000] "GET / HTTP/1.1" 500 83393 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.21 Safari/537.36" "-"
backend_1   | [17/Dec/2016 08:26:13] "GET /favicon.ico HTTP/1.0" 500 83568
nginx_1     | 172.18.0.1 - - [17/Dec/2016:08:26:13 +0000] "GET /favicon.ico HTTP/1.1" 500 83668 "http://localhost:8000/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.21 Safari/537.36" "-"
backend_1   | [17/Dec/2016 08:26:20] "GET / HTTP/1.0" 500 83293
nginx_1     | 172.18.0.1 - - [17/Dec/2016:08:26:20 +0000] "GET / HTTP/1.1" 500 83400 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.21 Safari/537.36" "-"
backend_1   | [17/Dec/2016 08:26:21] "GET /favicon.ico HTTP/1.0" 500 83568
nginx_1     | 172.18.0.1 - - [17/Dec/2016:08:26:21 +0000] "GET /favicon.ico HTTP/1.1" 500 83668 "http://localhost:8000/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.21 Safari/537.36" "-"
 11% building modules 15/53 modules 38 active ...de_modules/redux/lib/utils/warning.jsnode_modules/nan
frontend_1  | resolve failed:  { Error: Cannot find module 'font-awesome'
frontend_1  |     at Function.Module._resolveFilename (module.js:469:15)
frontend_1  |     at Function.requireRelative.resolve (/django/node_modules/require-relative/index.js:30:17)
frontend_1  |     at resolve (/django/node_modules/modify-babel-preset/lib/serialize.js:26:26)
frontend_1  |     at findAndRemove (/django/node_modules/modify-babel-preset/lib/serialize.js:83:11)
frontend_1  |     at /django/node_modules/modify-babel-preset/lib/serialize.js:126:13
frontend_1  |     at Array.map (native)
frontend_1  |     at loadPreset (/django/node_modules/modify-babel-preset/lib/serialize.js:118:29)
frontend_1  |     at module.exports (/django/node_modules/modify-babel-preset/index.js:95:19)
frontend_1  |     at Object.<anonymous> (/django/node_modules/babel-preset-es2015-loose/index.js:5:18)
frontend_1  |     at Module._compile (module.js:570:32)
frontend_1  |     at Object.Module._extensions..js (module.js:579:10)
frontend_1  |     at Module.load (module.js:487:32)
frontend_1  |     at tryModuleLoad (module.js:446:12)
frontend_1  |     at Function.Module._load (module.js:438:3)
frontend_1  |     at Module.require (module.js:497:17)
frontend_1  |     at require (internal/module.js:20:19)
frontend_1  |     at /django/node_modules/babel-core/lib/transformation/file/options/option-manager.js:302:17
frontend_1  |     at Array.map (native)
frontend_1  |     at OptionManager.resolvePresets (/django/node_modules/babel-core/lib/transformation/file/options/option-manager.js:270:20)
frontend_1  |     at OptionManager.mergePresets (/django/node_modules/babel-core/lib/transformation/file/options/option-manager.js:259:10)
frontend_1  |     at OptionManager.mergeOptions (/django/node_modules/babel-core/lib/transformation/file/options/option-manager.js:244:14)
frontend_1  |     at OptionManager.init (/django/node_modules/babel-core/lib/transformation/file/options/option-manager.js:374:12)
frontend_1  |     at File.initOptions (/django/node_modules/babel-core/lib/transformation/file/index.js:216:65)
frontend_1  |     at new File (/django/node_modules/babel-core/lib/transformation/file/index.js:139:24)
frontend_1  |     at Pipeline.transform (/django/node_modules/babel-core/lib/transformation/pipeline.js:46:16)
frontend_1  |     at transpile (/django/node_modules/babel-loader/lib/index.js:41:20)
frontend_1  |     at Object.module.exports (/django/node_modules/babel-loader/lib/index.js:138:12)
frontend_1  |     at LOADER_EXECUTION (/django/node_modules/loader-runner/lib/LoaderRunner.js:114:14)
frontend_1  |     at runSyncOrAsync (/django/node_modules/loader-runner/lib/LoaderRunner.js:115:4)
frontend_1  |     at iterateNormalLoaders (/django/node_modules/loader-runner/lib/LoaderRunner.js:224:2) code: 'MODULE_NOT_FOUND' } font-awesome
frontend_1  | resolve failed:  { Error: Cannot find module 'eslint-module-utils'
frontend_1  |     at Function.Module._resolveFilename (module.js:469:15)
frontend_1  |     at Function.requireRelative.resolve (/django/node_modules/require-relative/index.js:30:17)
frontend_1  |     at resolve (/django/node_modules/modify-babel-preset/lib/serialize.js:26:26)
frontend_1  |     at findAndRemove (/django/node_modules/modify-babel-preset/lib/serialize.js:83:11)
frontend_1  |     at /django/node_modules/modify-babel-preset/lib/serialize.js:126:13
frontend_1  |     at Array.map (native)
frontend_1  |     at loadPreset (/django/node_modules/modify-babel-preset/lib/serialize.js:118:29)
frontend_1  |     at module.exports (/django/node_modules/modify-babel-preset/index.js:95:19)
frontend_1  |     at Object.<anonymous> (/django/node_modules/babel-preset-es2015-loose/index.js:5:18)
frontend_1  |     at Module._compile (module.js:570:32)
frontend_1  |     at Object.Module._extensions..js (module.js:579:10)
frontend_1  |     at Module.load (module.js:487:32)
frontend_1  |     at tryModuleLoad (module.js:446:12)
frontend_1  |     at Function.Module._load (module.js:438:3)
frontend_1  |     at Module.require (module.js:497:17)
frontend_1  |     at require (internal/module.js:20:19)
frontend_1  |     at /django/node_modules/babel-core/lib/transformation/file/options/option-manager.js:302:17
frontend_1  |     at Array.map (native)
frontend_1  |     at OptionManager.resolvePresets (/django/node_modules/babel-core/lib/transformation/file/options/option-manager.js:270:20)
frontend_1  |     at OptionManager.mergePresets (/django/node_modules/babel-core/lib/transformation/file/options/option-manager.js:259:10)
frontend_1  |     at OptionManager.mergeOptions (/django/node_modules/babel-core/lib/transformation/file/options/option-manager.js:244:14)
frontend_1  |     at OptionManager.init (/django/node_modules/babel-core/lib/transformation/file/options/option-manager.js:374:12)
frontend_1  |     at File.initOptions (/django/node_modules/babel-core/lib/transformation/file/index.js:216:65)
frontend_1  |     at new File (/django/node_modules/babel-core/lib/transformation/file/index.js:139:24)
frontend_1  |     at Pipeline.transform (/django/node_modules/babel-core/lib/transformation/pipeline.js:46:16)
frontend_1  |     at transpile (/django/node_modules/babel-loader/lib/index.js:41:20)
frontend_1  |     at Object.module.exports (/django/node_modules/babel-loader/lib/index.js:138:12)
frontend_1  |     at LOADER_EXECUTION (/django/node_modules/loader-runner/lib/LoaderRunner.js:114:14)
frontend_1  |     at runSyncOrAsync (/django/node_modules/loader-runner/lib/LoaderRunner.js:115:4)
frontend_1  |     at iterateNormalLoaders (/django/node_modules/loader-runner/lib/LoaderRunner.js:224:2) code: 'MODULE_NOT_FOUND' } eslint-module-utils
frontend_1  | resolve failed:  { Error: Cannot find module 'caniuse-db'
frontend_1  |     at Function.Module._resolveFilename (module.js:469:15)
frontend_1  |     at Function.requireRelative.resolve (/django/node_modules/require-relative/index.js:30:17)
frontend_1  |     at resolve (/django/node_modules/modify-babel-preset/lib/serialize.js:26:26)
frontend_1  |     at findAndRemove (/django/node_modules/modify-babel-preset/lib/serialize.js:83:11)
frontend_1  |     at /django/node_modules/modify-babel-preset/lib/serialize.js:126:13
frontend_1  |     at Array.map (native)
frontend_1  |     at loadPreset (/django/node_modules/modify-babel-preset/lib/serialize.js:118:29)
frontend_1  |     at module.exports (/django/node_modules/modify-babel-preset/index.js:95:19)
frontend_1  |     at Object.<anonymous> (/django/node_modules/babel-preset-es2015-loose/index.js:5:18)
frontend_1  |     at Module._compile (module.js:570:32)
frontend_1  |     at Object.Module._extensions..js (module.js:579:10)
frontend_1  |     at Module.load (module.js:487:32)
frontend_1  |     at tryModuleLoad (module.js:446:12)
frontend_1  |     at Function.Module._load (module.js:438:3)
frontend_1  |     at Module.require (module.js:497:17)
frontend_1  |     at require (internal/module.js:20:19)
frontend_1  |     at /django/node_modules/babel-core/lib/transformation/file/options/option-manager.js:302:17
frontend_1  |     at Array.map (native)
frontend_1  |     at OptionManager.resolvePresets (/django/node_modules/babel-core/lib/transformation/file/options/option-manager.js:270:20)
frontend_1  |     at OptionManager.mergePresets (/django/node_modules/babel-core/lib/transformation/file/options/option-manager.js:259:10)
frontend_1  |     at OptionManager.mergeOptions (/django/node_modules/babel-core/lib/transformation/file/options/option-manager.js:244:14)
frontend_1  |     at OptionManager.init (/django/node_modules/babel-core/lib/transformation/file/options/option-manager.js:374:12)
frontend_1  |     at File.initOptions (/django/node_modules/babel-core/lib/transformation/file/index.js:216:65)
frontend_1  |     at new File (/django/node_modules/babel-core/lib/transformation/file/index.js:139:24)
frontend_1  |     at Pipeline.transform (/django/node_modules/babel-core/lib/transformation/pipeline.js:46:16)
frontend_1  |     at transpile (/django/node_modules/babel-loader/lib/index.js:41:20)
frontend_1  |     at Object.module.exports (/django/node_modules/babel-loader/lib/index.js:138:12)
frontend_1  |     at LOADER_EXECUTION (/django/node_modules/loader-runner/lib/LoaderRunner.js:114:14)
frontend_1  |     at runSyncOrAsync (/django/node_modules/loader-runner/lib/LoaderRunner.js:115:4)
frontend_1  |     at iterateNormalLoaders (/django/node_modules/loader-runner/lib/LoaderRunner.js:224:2) code: 'MODULE_NOT_FOUND' } caniuse-db
frontend_1  | resolve failed:  { Error: Cannot find module 'babel-runtime'
frontend_1  |     at Function.Module._resolveFilename (module.js:469:15)
frontend_1  |     at Function.requireRelative.resolve (/django/node_modules/require-relative/index.js:30:17)
frontend_1  |     at resolve (/django/node_modules/modify-babel-preset/lib/serialize.js:26:26)
frontend_1  |     at findAndRemove (/django/node_modules/modify-babel-preset/lib/serialize.js:83:11)
frontend_1  |     at /django/node_modules/modify-babel-preset/lib/serialize.js:126:13
frontend_1  |     at Array.map (native)
frontend_1  |     at loadPreset (/django/node_modules/modify-babel-preset/lib/serialize.js:118:29)
frontend_1  |     at module.exports (/django/node_modules/modify-babel-preset/index.js:95:19)
frontend_1  |     at Object.<anonymous> (/django/node_modules/babel-preset-es2015-loose/index.js:5:18)
frontend_1  |     at Module._compile (module.js:570:32)
frontend_1  |     at Object.Module._extensions..js (module.js:579:10)
frontend_1  |     at Module.load (module.js:487:32)
frontend_1  |     at tryModuleLoad (module.js:446:12)
frontend_1  |     at Function.Module._load (module.js:438:3)
frontend_1  |     at Module.require (module.js:497:17)
frontend_1  |     at require (internal/module.js:20:19)
frontend_1  |     at /django/node_modules/babel-core/lib/transformation/file/options/option-manager.js:302:17
frontend_1  |     at Array.map (native)
frontend_1  |     at OptionManager.resolvePresets (/django/node_modules/babel-core/lib/transformation/file/options/option-manager.js:270:20)
frontend_1  |     at OptionManager.mergePresets (/django/node_modules/babel-core/lib/transformation/file/options/option-manager.js:259:10)
frontend_1  |     at OptionManager.mergeOptions (/django/node_modules/babel-core/lib/transformation/file/options/option-manager.js:244:14)
frontend_1  |     at OptionManager.init (/django/node_modules/babel-core/lib/transformation/file/options/option-manager.js:374:12)
frontend_1  |     at File.initOptions (/django/node_modules/babel-core/lib/transformation/file/index.js:216:65)
frontend_1  |     at new File (/django/node_modules/babel-core/lib/transformation/file/index.js:139:24)
frontend_1  |     at Pipeline.transform (/django/node_modules/babel-core/lib/transformation/pipeline.js:46:16)
frontend_1  |     at transpile (/django/node_modules/babel-loader/lib/index.js:41:20)
frontend_1  |     at Object.module.exports (/django/node_modules/babel-loader/lib/index.js:138:12)
frontend_1  |     at LOADER_EXECUTION (/django/node_modules/loader-runner/lib/LoaderRunner.js:114:14)
frontend_1  |     at runSyncOrAsync (/django/node_modules/loader-runner/lib/LoaderRunner.js:115:4)
frontend_1  |     at iterateNormalLoaders (/django/node_modules/loader-runner/lib/LoaderRunner.js:224:2) code: 'MODULE_NOT_FOUND' } babel-runtime
frontend_1  | Version: webpack 2.1.0-beta.15
frontend_1  | Time: 55231ms
frontend_1  |                                                   Asset       Size  Chunks             Chunk Names
frontend_1  |                 /fonts/glyphicons-halflings-regular.ttf    45.4 kB          [emitted]  
frontend_1  |                 /fonts/glyphicons-halflings-regular.eot    20.1 kB          [emitted]  
frontend_1  | /images/react-logo.png?bf6e7aa4366ba93442e42038897d683d    35.1 kB          [emitted]  
frontend_1  | /images/redux-logo.png?59c467536111a981d904a050d335c2be     218 kB          [emitted]  
frontend_1  |                /fonts/glyphicons-halflings-regular.woff    23.4 kB          [emitted]  
frontend_1  |                         /fonts/fontawesome-webfont.woff      98 kB          [emitted]  
frontend_1  |               /fonts/glyphicons-halflings-regular.woff2      18 kB          [emitted]  
frontend_1  |                        /fonts/fontawesome-webfont.woff2    77.2 kB          [emitted]  
frontend_1  |                          /fonts/fontawesome-webfont.eot     166 kB          [emitted]  
frontend_1  |                          /fonts/fontawesome-webfont.ttf     166 kB          [emitted]  
frontend_1  |                 /fonts/glyphicons-halflings-regular.svg     109 kB          [emitted]  
frontend_1  |                          /fonts/fontawesome-webfont.svg     444 kB          [emitted]  
frontend_1  |                          vendor.3962ffc3e7f549f8c9e3.js    1.74 MB       0  [emitted]  vendor
frontend_1  |                             app.3962ffc3e7f549f8c9e3.js     656 kB       1  [emitted]  app
frontend_1  |                      vendor.3962ffc3e7f549f8c9e3.js.map    2.19 MB       0  [emitted]  vendor
frontend_1  |                         app.3962ffc3e7f549f8c9e3.js.map     822 kB       1  [emitted]  app
frontend_1  |                                              index.html  441 bytes          [emitted]  
frontend_1  | [1078] multi vendor 172 bytes {0} [built]
frontend_1  |     + 1086 hidden modules
frontend_1  | Child html-webpack-plugin for "index.html":
frontend_1  |         + 4 hidden modules
backend_1   | [17/Dec/2016 08:28:03] "GET / HTTP/1.0" 200 441
nginx_1     | 172.18.0.1 - - [17/Dec/2016:08:28:03 +0000] "GET / HTTP/1.1" 200 453 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.21 Safari/537.36" "-"
nginx_1     | 172.18.0.1 - - [17/Dec/2016:08:28:03 +0000] "GET /static/app.3962ffc3e7f549f8c9e3.js?3962ffc3e7f549f8c9e3 HTTP/1.1" 200 656421 "http://localhost:8000/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.21 Safari/537.36" "-"
backend_1   | [17/Dec/2016 08:28:03] "GET /static/app.3962ffc3e7f549f8c9e3.js?3962ffc3e7f549f8c9e3 HTTP/1.0" 200 656421
backend_1   | [17/Dec/2016 08:28:03] "GET /static/vendor.3962ffc3e7f549f8c9e3.js?3962ffc3e7f549f8c9e3 HTTP/1.0" 200 1736691
nginx_1     | 172.18.0.1 - - [17/Dec/2016:08:28:03 +0000] "GET /static/vendor.3962ffc3e7f549f8c9e3.js?3962ffc3e7f549f8c9e3 HTTP/1.1" 200 1736691 "http://localhost:8000/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.21 Safari/537.36" "-"
nginx_1     | 172.18.0.1 - - [17/Dec/2016:08:28:03 +0000] "GET /static/fonts/fontawesome-webfont.woff2 HTTP/1.1" 200 77160 "http://localhost:8000/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.21 Safari/537.36" "-"
backend_1   | [17/Dec/2016 08:28:03] "GET /static/fonts/fontawesome-webfont.woff2 HTTP/1.0" 200 77160
backend_1   | [17/Dec/2016 08:28:03] "GET /static/images/react-logo.png?bf6e7aa4366ba93442e42038897d683d HTTP/1.0" 200 35133
nginx_1     | 172.18.0.1 - - [17/Dec/2016:08:28:03 +0000] "GET /static/images/react-logo.png?bf6e7aa4366ba93442e42038897d683d HTTP/1.1" 200 35133 "http://localhost:8000/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.21 Safari/537.36" "-"
nginx_1     | 172.18.0.1 - - [17/Dec/2016:08:28:03 +0000] "GET /static/images/redux-logo.png?59c467536111a981d904a050d335c2be HTTP/1.1" 200 217989 "http://localhost:8000/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.21 Safari/537.36" "-"
backend_1   | [17/Dec/2016 08:28:03] "GET /static/images/redux-logo.png?59c467536111a981d904a050d335c2be HTTP/1.0" 200 217989
backend_1   | [17/Dec/2016 08:28:04] "GET /favicon.ico HTTP/1.0" 200 441
nginx_1     | 172.18.0.1 - - [17/Dec/2016:08:28:04 +0000] "GET /favicon.ico HTTP/1.1" 200 453 "http://localhost:8000/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.21 Safari/537.36" "-"

`npm run coverage` error.

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

Include celery

Add example celery 4 tasks

css order with CommonsChunkPlugin

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.

sessionStorage over localStorage

I noticed in src/static/actions/auth.js that sessionStorage is being used over localStorage. Wouldn't typical behavior be to persist a user's session even when the browser gets closed?

Happy to submit a PR - just wanted to know if there's a rationale I'm missing.

HELP - How to deploy this to AWS EC2?

Login is not working, because the JS endpoint is hardcoded to a specific IP address

See PR #1

Thank you.

Login issues

After I login using via /login then i try to access /admin/, why does it prompt me to login again?

Postgres errors on docker-compose up

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...

Postgres not persisting data to shared volumes between runs

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

Recommend Projects

React

A declarative, efficient, and flexible JavaScript library for building user interfaces.
Vue.js

🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript

TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
TensorFlow

An Open Source Machine Learning Framework for Everyone
Django

The Web framework for perfectionists with deadlines.
Laravel

A PHP framework for web artisans
D3

Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

javascript

JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
web

Some thing interesting about web. New door for the world.
server

A server is a program made to process requests and deliver data to clients.
Machine learning

Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Visualization

Some thing interesting about visualization, use data art
Game

Some thing interesting about game, make everyone happy.

Recommend Org

Facebook

We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft

Open source projects and samples from Microsoft.
Google

Google ❤️ Open Source for everyone.
Alibaba

Alibaba Open Source for everyone
D3

Data-Driven Documents codes.
Tencent

China tencent open source team.

Jobs

Jooble