What is the method for adding changes after deploy...
# replication-troubleshooting
s
What is the method for adding changes after deploying airbyte in GCP? I need to make changes to the nginx config template and rebuild the image, but I can't access the airbyte-proxy folder from gcloud terminal like i would in my local machine
m
@Evan Tahler (Airbyte) do you have any thoughts about this?
e
We haven't added the airbyte-proxy container to our helm charts yet (cc @Topher (Airbyte)), so I don't really have much advice about how to use it on GCP yet. It's only for use in docker-compose deployments at the moment
u
I don't think they're deploying on Kubernetes, it is only GCP.
e
Can you share more about what that means? Is it just a regular server running docker-compose?
b
I have the same issue myself. Slightly different maybe. I am trying to move the existing airbyte postgres db to a external postgres db I have created in an additional persistent disk. I am trying to follow this tutorial but I cannot seem to find where the
.env.
file would be: https://docs.airbyte.com/operator-guides/configuring-airbyte-db
e
b
Hi @Evan Tahler (Airbyte) thanks for your reply. I don't seem to have this file. In fact my
/tmp/airbyte_local
is empty. Should I place this
.env.
file there? I'm using a airbyte open source install on GCP and docker.
e
It wouldn’t be in tmp, it’s where you cloned the repo too and you run docker-compose from
b
Thank you very much Evan. I can take it form here. I really appreciate the help.
s
@Evan Tahler @Marcos Marx (Airbyte) thanks for responding. I have deployed it on a compute engine VM with docker by following the steps of this guide exactly: https://docs.airbyte.com/deploying-airbyte/on-gcp-compute-engine/
hi guys, update - i managed to find a way to do it. Please do let me know if there is another best practice method but here's what I did: • Use gcloud scp command to copy over my updated airbyte-proxy folder from local to the vm (https://cloud.google.com/compute/docs/instances/transfer-files#transfergcloud) • edit docker-compose.yaml in the virtual machine and remove the line
image: airbyte/proxy:${VERSION}
and replace it with this build subsection pointing to my copied folder:
build:
context: "./airbyte-proxy"
👏 1
u
This is a good startegy Stuart, today there isn't a better approach (I think so)
👍 1