Add support for using a SOCKS5 proxy to connect to live replica database #25
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This should be documented somewhere, but for now the steps are:
~/.ssh/config
so you can easily login to toolforgessh -D 0.0.0.0:1080 login.toolforge.org
default_config.yaml
or add aconfig.yaml
in the same directory, with values for the keys:REPLICA_SOCKS5_PROXY_HOST
-- The IP or hostname of the Docker host where the proxy is running.REPLICA_SOCKS5_PROXY_PORT
-- The port you used for -D aboveREPLICA_DOMAIN
-- Set to:'analytics.db.svc.wikimedia.cloud'
REPLICA_USER
-- Your MariaDB credentials, found in replica.my.cnf in your toolforge home directoryREPLICA_PASSWORD
-- Same as above, but the passwordAlso this PR removes some values from default_config that aren't referenced anywhere in the code (
REPLICA_DOMAIN
andREPLICA_HOST
)