Single compose file

[thomas-gerber]

Description

On windows, one sees local volume related errors (see #173 and this slack thread). However, we noticed that:

1. on that same machine, one could start vanilla airbyte with docker compose (see airbyte documentation)
2. on that same machine, docker-compose -f airbyte-services.yaml up did not have any volume issues (i.e. airbyte-server got successfully created.

Hence, there may be some issues with the extends keyword, which is not surprising given its checkered history (here, and here).

The fix is to group everything into a single compose file.
Fixes #173

Type of change

• Bug fix (non-breaking change which fixes an issue)

Checklist

(Delete what does not apply)

• Have you checked to there aren't other open Pull Requests for the same update/change?
• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you successfully run tests with your changes locally?

[thomas-gerber]

Currently being tested by a windows user.

[thomas-gerber]

Tested on

• Windows 10.0.19044 (Windows 10 Pro)
• Docker Desktop for Windows 4.12.0 (85629) with WSL2 as doc suggests (I was prompted by docker desktop to do this
  Ingested some data.
  It works!

[thomas-gerber]

@ypc-faros could you check if I got the profiles correct?

[tovbinm]

Awesome!

Let's put comments around the section from the original Airbyte compose file so it would be easier for us to merge with upstream later on.

[thomas-gerber]

Awesome!

Let's put comments around the section from the original Airbyte compose file so it would be easier for us to merge with upstream later on.

Already done

[ypc-faros]

@ypc-faros could you check if I got the profiles correct?

Looks good 👍