where is official docker compose documentations for port binding @kapa.ai?

The official Docker Compose documentation for port binding can be found at the following link: [Docker Compose File Reference](https://docs.docker.com/compose/compose-file/compose-file-v3/#ports) In the

ports

section, you can specify the IP address and port number for the service. Here is an example:

yaml services:   some-service:     ports:       - "192.168.1.100:8080:8080"

In this example, the service

some-service

is only accessible at the IP address 192.168.1.100 on port 8080.

To modify your Docker Compose configuration without losing data from your previous deployment, you should follow these steps: 1. Backup your data: Before making any changes, it's always a good idea to backup your data. In Airbyte, you can export your configurations via the UI or API. This will generate a tarball (

tar.gz

) file containing your configurations. 2. Modify Docker Compose Configuration: Make the necessary changes to your

docker-compose.yaml

file. This could be changing the port bindings, environment variables, or adding/removing services. 3. Re-deploy Airbyte: With the updated configurations, you're ready to deploy your Airbyte application by running

docker compose up

. 4. Import your data: After the deployment, you can import your configurations back into Airbyte via the UI or API. Here is an example of how to export and import configurations via the API: Export:

bash curl -H "Content-Type: application/json" -X POST localhost:8000/api/v1/deployment/export --output /tmp/airbyte_archive.tar.gz

Import:

bash curl -H "Content-Type: application/json" -X POST localhost:8000/api/v1/deployment/import --data-binary "@/tmp/airbyte_archive.tar.gz"

Please note that the exact commands might vary depending on your setup and the version of Airbyte you're using. Always refer to the [official Airbyte documentation](https://docs.airbyte.com/) for the most accurate information. Source: [Upgrading Airbyte on K8s](https://docs.airbyte.com/operator-guides/upgrading-airbyte)

Starting from Airbyte version 0.40.7, the export and import of configurations through the Airbyte UI has been removed. Instead, you should use the Octavia CLI tool for exporting and importing Airbyte configurations. Here's how you can do it: 1. Set up Octavia CLI: First, you need to set up the Octavia CLI on your machine. You can do this by defining an alias for the Octavia CLI Docker image. Replace

0.40.18

with your specific Airbyte version.

bash OCTAVIA_CLI=0.40.18 OCTAVIA_ENV_FILE=/home/ari/.octavia export OCTAVIA_ENABLE_TELEMETRY=True alias octavia="docker run -i --rm -v \$(pwd):/home/octavia-project --network host --env-file \${OCTAVIA_ENV_FILE} --user \$(id -u):\$(id -g) airbyte/octavia-cli:${OCTAVIA_CLI}"

2. Export Configurations: You can export your configurations by initializing an Octavia project and then importing all configurations from your Airbyte instance.

bash mkdir airbyte-configuration && cd airbyte-configuration octavia init octavia import all

3. Import Configurations: To import your configurations into a new Airbyte instance, you can use the

octavia apply all

command.

bash octavia apply all

Please note that you need to have the

AIRBYTE_USERNAME

and

AIRBYTE_PASSWORD

environment variables in the

.octavia

file if you are using Airbyte version 0.40.16 or above that comes with Basic Authentication for the webapp, API, and CLI. For more detailed instructions, you can refer to the [official Airbyte tutorial on version controlling Airbyte configurations with Octavia CLI](https://airbyte.com/tutorials/version-control-airbyte-configurations). Sources: - [Airbyte Slack Conversation](https://airbytehq.slack.com/archives/C021JANJ6TY/p1667231499430979) - [Airbyte Tutorial: Version control Airbyte configurations with Octavia CLI](https://airbyte.com/tutorials/version-control-airbyte-configurations)