Docker compose

[bar9]

Docker-Compose setup with documentation

[TheFern2]

@bar9 I'll test this docker config sometime in the weekend. I think both Dockerfile, and docker-compose.yml should be Dockerfile.example kind of like the .env.example so if a user wants to make changes they won't need to worry about git tracking those changes. And then Dockerfile and docker-compose.yml should be on gitignore.

Another note, on the Dockerfile I see expose 8080, but not 5432, is that OK? Or should that port be exposed too?
I tried to run and kept getting stories db doesn't exists, isn't that something that can be configured with docker?

[bar9]

@bar9 I'll test this docker config sometime in the weekend. I think both Dockerfile, and docker-compose.yml should be Dockerfile.example kind of like the .env.example so if a user wants to make changes they won't need to worry about git tracking those changes. And then Dockerfile and docker-compose.yml should be on gitignore.

Yes, that makes sense

Another note, on the Dockerfile I see expose 8080, but not 5432, is that OK? Or should that port be exposed too?

No, we use the official postgres image in the compose file, they have already taken care of this

I tried to run and kept getting stories db doesn't exists, isn't that something that can be configured with docker?

Yes, we could do it with a startup script in the API container. Would probably requires some additional "wait-for"-loop so it only runs when the DB is ready