Purpose: this is a purely for educational and reproduction purposes. Running this locally is quick and easy, but if running a production instance of Sauce Connect (or many instances) follow the official Kubernetes documentation or deployment of your choice.
cd to a directory of your choosing.
docker compose up and watch the Sauce Connect Proxies start!
The Sauce Connect Proxy sits adjacent to a nginx:latest instance. This means you can reach the nginx service from Sauce Labs by going to nginx (if you run it as is). You can also play around and provide the container a name with container_name.
For example, Start the docker containers. Go to a Live Web Session on app.saucelabs.com. Go to http://nginx:80 (leaving the yaml file as is). You should see a Welcome to Nginx page.
container_name: mockserver would be reachable from any app or website that tried to hit mockserver via HTTP. This is due to the nature of how docker resolves container names for any valid entries on that docker network. Read more https://docs.docker.com/config/containers/container-networking/#:~:text=In%20the%20same,on%20that%20network.
If you need a Sauce Connect Proxy to stay up indefinitely. Some organizations, large or small, need a set of shared Sauce Connect Pools that automatically restart when they go down.