fix(docker-compose): fix volumes paths for rabbitmq

[bcdady]

Also makes docker_setup.sh compatible to run on MacOS (for development)

[bcdady]

Addresses issue #4

[robertcoopercode]

Hi @bcdady, thanks for the PR! We will try to take a look at this, but it's not a priority right now. We were able to successfully setup a new self-hosted customer this week using the current docker-compose.yml file, so i'm not certain why you ran into issues with it. My intuition is that you might be using a newer version of the docker-compose CLI which uses slightly different syntax in the docker-compose.yml file. Our setup script downloads a pinned version of the docker-compose CLI (https://github.com/Basedash/self-hosted/blob/main/get-docker-compose.sh) that works with the current docker-compose.yml file.

[robertcoopercode]

Clever!

[bcdady]

Our setup script downloads a pinned version of the docker-compose CLI (https://github.com/Basedash/self-hosted/blob/main/get-docker-compose.sh) that works with the current docker-compose.yml file.

That could be. Since I already have docker (podman) and docker-compose setup on my dev machine, I didn't need or want to redownload via the setup scripts.
I think it would be better to, instead of running docker compose on a virtual server, support running the containerized workload on a serverless framework, or on Kubernetes, such as via Helm chart.

[bcdady]

Our setup script downloads a pinned version of the docker-compose CLI (https://github.com/Basedash/self-hosted/blob/main/get-docker-compose.sh) that works with the current docker-compose.yml file.

There are quite a few releases of docker-compose CLI available since the version specified in the script (1.29). Why is the setup script pinned to such a seemingly far backdated version/tag?

[bcdady]

This is the most essential part of the fix, to play nice with more recent versions of docker-compose.

[robertcoopercode]

Our setup script downloads a pinned version of the docker-compose CLI (https://github.com/Basedash/self-hosted/blob/main/get-docker-compose.sh) that works with the current docker-compose.yml file.

That could be. Since I already have docker (podman) and docker-compose setup on my dev machine, I didn't need or want to redownload via the setup scripts. I think it would be better to, instead of running docker compose on a virtual server, support running the containerized workload on a serverless framework, or on Kubernetes, such as via Helm chart.

We provide the docker-compose method as one way to run a self-hosted version of Basedash, but it is still possible to run it via Kubernetes and helm charts. For example, we were able to use AWS Cloudformation to spin up a self-hosted version of Basedash (see here for the cloudformation template).

[robertcoopercode]

here are quite a few releases of docker-compose CLI available since the version specified in the script (1.29). Why is the setup script pinned to such a seem

We simply haven't gotten around to upgrading to a newer version.