Docker cleanups

- Put docker-compose.yml into version control, no need to make this an example
  file and complicate things.
- Start the docker dev-env osem on port 3000. Just as our documentation says
  and how we do it in vagrant.
- hardcode CONTAINER_USERID so you don't have to have an
  docker-compose.override.yml if your UID is 1000.
- Rename web service/container to osem for clarity in the logs
- Keep assets also in a volume in production
- warn a bit more prominently about docker-compose.override.yml

.gitignore

@@ -35,7 +35,6 @@ pickle-email-*.html
 .env.development
 .env.test
 .env.local
-docker-compose.yml
 docker-compose.override.yml
 .DS_Store
 .byebug_history

CONTRIBUTING.md

@@ -27,6 +27,17 @@ based development environment, based on [docker](https://www.docker.com/) and
 [docker-compose](https://docs.docker.com/compose/). Here's a step by step guide
 how to set it up.
 
+**WARNING**: Since we mount the repository into our container, your user id and
+the id of the osem user inside the container need to be the same. If your user
+id (`id -u`) is something else than `1000` you can copy the docker-compose
+override example file and in it, set your user id in the variable
+*CONTAINER_USERID*.
+
+```bash
+sed "s/13042/`id -u`/" docker-compose.override.yml.example > docker-compose.override.yml
+```
+
+
 1. Set up the development environment:
     ```bash
     docker-compose run --rm osem bundle exec rake setup:bootstrap
@@ -54,13 +65,6 @@ how to set it up.
     docker-compose exec osem_1 /bin/bash -l
     ```
 
-**WARNING**: Since we mount the repository into our container, your user id and the id of the osem user inside the container need to be the same. If your user id (`id -u`) is something else than `1000` you can copy the docker-compose override example file and in it, set your user id in the variable
-*CONTAINER_USERID*.
-
-```bash
-cp docker-compose.override.yml.example docker-compose.override.yml
-```
-
 ### with Vagrant
 Another option is using [Vagrant](https://www.vagrantup.com/) and [VirtualBox 5.0.10](https://www.virtualbox.org/wiki/Download_Old_Builds_5_0) to create your development environment.
 

bin/osem-init.sh

@@ -1,3 +1,5 @@
 #!/bin/bash
+# Setup the app if it isn't already setup
 bundle exec rake setup:bootstrap
-foreman start
+# Start the app
+foreman start -p 3000

docker-compose.yml

@@ -5,13 +5,15 @@ services:
     image: postgres
     environment:
       PGDATA: /var/lib/postgresql/data/pgdata
-  web:
-    build: .
-    # env_file: dotenv.example
+  osem:
+    build:
+      context: .
+      args:
+        CONTAINER_USERID: 1000
     command: /osem/bin/osem-init.sh 
     depends_on:
       - database
     ports:
-      - 5000:5000
+      - 3000:3000
     volumes:
       - .:/osem

docker-compose.yml.production-example

@@ -7,21 +7,23 @@ services:
       PGDATA: /var/lib/postgresql/data/pgdata
     volumes:
       - database:/var/lib/postgresql/data/pgdata
-  web:
+  osem:
     build: .
     dockerfile: Dockerfile.production
     env_file: .env.production # see dotenv.example file
     depends_on:
       - database
     ports:
-      - 5000:5000
+      - 3000:3000
     volumes:
       - .:/osem
       - web-data:/osem/public/system
+      - web-assets:/osem/public/assets
       - web-logs:/osem/log
 
 # named volumes to persist data
 volumes:
   database:
   web-data:
+  web-assets:
   web-logs: