Open erik-pineiro-github opened 2 years ago
Hey @erik-pineiro-github, thanks for filing the PR. In my mind we should attack this by linking the example file in the documentation to this GitHub repository rather than changing the port designation here.
Just to clarify, why is this port needing to be exposed on the Docker host? The connect-sync
container is responsible for connecting to 1Password.com to sync vault data, and should not require any ingress whatsoever.
After confirming with @edif2008, the Connect Sync container should also have ports mapped per the example found in the developer documentation.