| |
@@ -32,16 +32,17 @@
|
| |
|
| |
./generate_client_secrets.sh
|
| |
|
| |
+ Although the Dockerfile runs the script to check if a client_secrets.json file is present, please generate it before starting the Docker container, so that client secrets are not being constantly generated every time the image is rebuilt.
|
| |
+
|
| |
#. Create a fas-admin-details.json file and add a json object with your FAS-Username and FAS-Password. See fas-admin-details.json.example.
|
| |
|
| |
#. Create a config.yml file and populate it with the user's details and usernames for `ADMINS <https://docs.djangoproject.com/en/2.1/ref/settings/#admins>`_ and superuser privileges respectively.
|
| |
|
| |
- Although the Dockerfile runs the script to check if a client_secrets.json file is present, please generate it before starting the Docker container, so that client secrets are not being constantly generated every time the image is rebuilt.
|
| |
-
|
| |
In order to run the web server, alongside the Redis queue and celery worker instance, simply run ``docker-compose up``.
|
| |
After this, you can access the local development server at ``http://localhost:8000/`` in your web browser.
|
| |
|
| |
- If you have made any changes to the code, the Docker image must be rebuilt; this can be done my running ``docker-compose up --build``.
|
| |
+ Auto reload of code changes is configured, so you shouldn't have to rebuild containers every time you make changes to the code base.
|
| |
+ If you have made any changes to the environment of the containers (eg - adding a new dependency), the Docker image must be rebuilt; this can be done my running ``docker-compose up --build``.
|
| |
|
| |
Since the code is being run in a container, we must enter the shell of the container in order to run tests.
|
| |
Access the shell of the Docker container by running ``docker-compose exec web sh``.
|
| |
I realize now this instruction is incorrect. In the container build instructions (i.e. Dockerfile), it generates client secrets whether asked or not. When we mount the volume in
docker-compose.yml
, it replaces all files copied into the container in the Dockerfile (even if some files are missing). In our case for development, I think it's better to omit this line for documentation along with the volume mount feedback above.