added a basic docker-compose file

[Kk-ships]

No description provided.

[nathan-isaac]

Is /data the correct volume location for the actual server data?

[matthewbahr]

Isn't it better to put the data in /usr/share/?

That's what my homeassistant docker compose does.

[nathan-isaac]

I just tested this locally on my machine. Seems to work good.

[fedme]

Looks good to me! (I am not a maintainer, just a random dev 😃)

[jlongster]

Is this still up-to-date given the latest docker file changes?

[Kk-ships]

@jlongster docker-compose file would be Dockerfile agnostic. I just builds a docker container based on Dockerfile contents.

[jlongster]

Yes but now we have two different docker files after #22, Dockerfile and Dockerfile.alpine. Does that make a difference?

[Kk-ships]

@jlongster build based on Dockerfile would be larger in size. If someone want's to use alpine build they can change dockerfile argument from Dockerfile to Dockerfile.alpine. Only difference would be container size.

[nathan-isaac]

To continue what @Kk-ships has said, it really depends on how we intend to use this docker-compose.yml file. In my experience, the docker-compose.yml file is mostly copied and modified for production use cases. The docker-compose.yml file in a project like this would mostly be for testing, development, and demo purposes. My suggestion would be to keep it pointing to the Dockerfile and if someone wants to change it they can create their own docker-compose.{name}.yml with the changes they want. Might be something we might want to add to the readme.

[jlongster]

Thanks, I'll add this!