Hello everyone! ❔ airbyte I want to run Airbyte on multiple different EC2 servers (so using the EC2 pulling the docker-compose file approach like here), but using some selfwritten connectors. My main headache right now is how to manage the code for those connectors. Anyone done something similar and could share their experiences on the approach? • Do you Git fork the Airbyte repository and add there whatever connectors and settings are needed and pull/deploy that to the specific servers • Do you have for each connector an own repository and push the image to Dockerhub for example and just use it in Airbyte? • Anything else I dont see? Did I oversee any documentation that already covering that topic? 🫣 Thanks in advance!

A message from kapa.ai

Gracias el bot 👍

We have several custom connectors, each has it's own git repo, CI pipeline, image repository, etc. Keep in mind that a recent "feature" requires semver-compliant tags for your connector images or airbyte will not start up. I am in the process of writing up an issue for this.