The followings scripts assume that Docker has already been installed.
They also assume that the user has Docker permissions without requiring sudo. If you do not have these permissions:
- Enter the following command:
sudo usermod -a -G docker $USER
- Log out and log back into your console to enable them.
wget https://raw.githubusercontent.com/hummingbot/gateway/main/docker/gateway-create.sh
wget https://raw.githubusercontent.com/hummingbot/gateway/main/docker/gateway-copy-certs.sh
chmod a+x *.sh
curl https://raw.githubusercontent.com/hummingbot/gateway/main/docker/gateway-create.sh -o gateway-create.sh
curl https://raw.githubusercontent.com/hummingbot/gateway/main/docker/gateway-copy-certs.sh -o gateway-copy-certs.sh
chmod a+x *.sh
This assumes that the user is using Windows Subsystem for Linux (WSL):
cd ~
curl https://raw.githubusercontent.com/hummingbot/gateway/main/docker/gateway-create.sh -o gateway-create.sh
curl https://raw.githubusercontent.com/hummingbot/gateway/main/docker/gateway-copy-certs.sh.sh -o gateway-copy-certs.sh.sh
chmod a+x *.sh
The gateway-create.sh script helps you pull, configure, and run the Gateway Docker image.
./gateway-create.sh
If you didn't do this step during gateway-create.sh, the gateway-copy-certs.sh script helps you copy the SSL certificates generated by Hummingbot into your Gateway files certs folder. This lets your Hummingbot instance access Gateway securely.
./gateway-copy-certs.sh
These commands assume a Gateway container with the default instance name gateway:
- List all Gateway containers:
docker ps -a --filter ancestor=hummingbot/gateway - Start Gateway container and attach to it:
docker start gateway && docker attach gateway - Stop Gateway container:
docker stop gateway - Update Gateway container to latest version:
docker pull hummingbot/gateway:latest - Remove Gateway container:
docker rm gateway