Hi, folks! Just joined the Slack, so definitely still finding my way around. That's to say if I'm not in the right place for my question, don't hesitate to point me to another channel. My question is likely very silly, but I cannot seem to find an answer to it anywhere (e.g. the forum, SO, etc. etc.). I'm confused about the [Deploy Airbyte Open Source](https://docs.airbyte.com/deploying-airbyte/on-aws-ec2/) approach of first installing Docker and Docker Compose on a VM, then clone the Airbyte repo, and finally running the code base with

docker-compose up -d

. It seems to me that the more straightforward approach would be to simply create your own repo with a Docker Compose file that effectively mirrors the one that ships with the codebase, but the total absence of any mention of this approach makes me suspect I'm overlooking something important. FYI, I've currently incorporated the docs for AWS into a Packer build that produces an AMI with all of the prerequisite technologies installed, so I'm not blocked by any means. I'm more anticipating the (possibly very obvious) question from my DevOps/SRE team about why I'm using Packer instead of just using Docker. Any and all information in greatly appreciated.

@[DEPRECATED] Marcos Marx turned this message into Zendesk ticket 2490 to ensure timely resolution!

Hey in the process you need to just download docker-compose file and the .env file

wget <https://raw.githubusercontent.com/airbytehq/airbyte/master/{.env,docker-compose.yaml}>

that should do and you don't need the whole repo and that is what should be there in the documentation. If you find something different kindly point me towards that.

Hey

Hi. Either way is good- your way is more scale and maintainable in the long run in prod mode since you can already quickly create CI\CD pipeline. the download local way is the easiest to get started and user friendly for those who are not familiar with your concept 🙂

@Harshith (Airbyte), 🤦 I cannot believe I didn't catch this. I see now: The call to the repo is really just grabbing those 2 files and not the entire codebase. That ... makes so much sense and I'm literally shaking my head and laughing out loud. Honestly, now that I see it, I can't unsee it, but if you put yourself in the shoes of someone who is 100% new to Airbyte and hopping around between deployment documentation, CDK docs, etc. etc. then it might also be clear that calling this out with a brief explanation might help drive the point home. The call to

wget

simply installs the

docker-compose.yaml

and

.env

file in the EC2 instance, and not the entire code base. Who knows, maybe it's just me. 🤷 In any case, I genuinely appreciate the help and feedback.

@Erik Eppel I agree with you! It's a simple adjust and could make total difference, mainly for new users of the doc. Sometimes we are tired and this detail goes unnoticed 😂