can anyone describe how you guys have setup your p...
# ask-ai
j
can anyone describe how you guys have setup your process for editing files in airbyte....ideally, i would be working locally and push to gitlab, then from there it would adjust the airbyte instance. would really appreciate insight into how you guys pull that off
k
A message from kapa.ai
To edit files in Airbyte locally, you can follow these steps: 1. Fork the Airbyte [repository](https://github.com/airbytehq/airbyte) on GitHub. 2. Clone the fork on your local machine:
Copy code
git clone [[email protected]](<https://docs.airbyte.com/cdn-cgi/l/email-protection>):{YOUR_USERNAME}/airbyte.git   cd airbyte
Or
Copy code
git clone <https://github.com/{YOUR_USERNAME}/airbyte.git>   cd airbyte
3. Test changes locally by installing the docs and running the server. For example, if you're working on documentation:
Copy code
cd docusaurus   yarn install   yarn start
Then navigate to http://localhost:3000/ to see your changes. 4. [Follow the GitHub workflow](https://docs.github.com/en/get-started/quickstart/contributing-to-projects/) to edit the files and create a pull request. Before your contributions are accepted, you'll need to sign the Contributor License Agreement (CLA). You will be prompted to sign the CLA while opening a pull request. 5. Assign
airbytehq/docs
as a Reviewer for your pull request. Source: [Contribute Documentation](https://docs.airbyte.com/contributing-to-airbyte/contribute-documentation) Regarding GitLab, the provided information is about setting up the GitLab Source connector in Airbyte, which is not directly related to your question about editing files and pushing to GitLab. However, you can adapt the GitHub workflow mentioned above to work with GitLab by following GitLab's documentation on [working with Git](https://docs.gitlab.com/ee/topics/git/) and [merge requests](https://docs.gitlab.com/ee/user/project/merge_requests/). Please note that the provided information is specific to contributing to Airbyte's documentation and repository. If you're working on your own Airbyte instance, you can follow a similar workflow by setting up your own GitLab repository and pushing changes to it.
j
@kapa.ai i want to edit files locally, and then push to a server instance that i have
k
A message from kapa.ai
To edit files locally and then push to a server instance, follow these steps: 1. Fork the Airbyte [repository](https://github.com/airbytehq/airbyte) ([source](https://docs.airbyte.com/contributing-to-airbyte/contribute-documentation)). 2. Clone the fork on your local machine:
Copy code
git clone <https://github.com/{YOUR_USERNAME}/airbyte.git>      cd airbyte
([source](https://docs.airbyte.com/contributing-to-airbyte/contribute-documentation)) 3. Make the necessary changes to the files on your local machine. 4. Test changes locally (if needed) by following the instructions in the [source](https://docs.airbyte.com/contributing-to-airbyte/contribute-documentation). 5. Commit your changes and push them to your forked repository. 6. [Follow the GitHub workflow](https://docs.github.com/en/get-started/quickstart/contributing-to-projects/) to create a pull request ([source](https://docs.airbyte.com/contributing-to-airbyte/contribute-documentation)). After your changes are merged, you can update your server instance Airbyte repository.
p
@Jake Kagan did you ever fix your deploy with docker-compose?
I had an issue with flags.yml and removed reference to the file to get my instance working
j
@Peter Cooper hey i ended up switching from podman to docker and it worked. i guess there's too much of a difference, you can't just swap the two out
👍 1
p
yeah I’m running smoothly in a docker compose, cool
j
@Peter Cooper yep, but now im stuck on an ssl error 😕
p
story of my life