This PR adds a very crude docker configuration. I just wanted to try out the app and was having problems with my wonky OSX python setup, so I set up a config to run it in docker instead.
It's very basic and has several issues, but since I did it I thought I'd submit it and we can iterate on it in the future.
Some flaws that should be fixed at some point:
~The sqlite database is not persistent across runs~ (EDIT: it actually is, but won't be when the next item is fixed)
The source code is mounted as a volume by default, should only be in development
There are no instructions in the README (which will still change rapidly anyway)
With this config, the following should be possible:
$ docker-compose up --build -d # Or without -d and run the rest in another terminal
$ docker-compose exec django python manage.py migrate
$ docker-compose exec django python manage.py createsuperuser
The back-end will then be exposed on localhost:8000 and front-end on localhost:3080 (not 3000 by default, which is already used by Gen 3 which many developers will run in parallel).
@djbusstop You can of course continue working in your regular environment without caring about the docker config.
This PR adds a very crude docker configuration. I just wanted to try out the app and was having problems with my wonky OSX python setup, so I set up a config to run it in docker instead.
It's very basic and has several issues, but since I did it I thought I'd submit it and we can iterate on it in the future.
Some flaws that should be fixed at some point:
With this config, the following should be possible:
The back-end will then be exposed on localhost:8000 and front-end on localhost:3080 (not 3000 by default, which is already used by Gen 3 which many developers will run in parallel).
@djbusstop You can of course continue working in your regular environment without caring about the docker config.