Snekway is reverse proxy tunnel for sneks with regions located in the same datacentres as the Battlesnake engine regions.
Installation
- snekway-x86_64-linux
- snekway-server-x86_64-linux
- snekway-aarch64-linux
- snekway-server-aarch64-linux
- snekway-x86_64-windows
Linux
wget https://vcdn.snekway.com/x86_64-linux/2023-r0/snekway
chmod +x snekway
./snekway --version
Usage
Usage: snekway [OPTIONS]
Options
-r REGION, --region=REGION Region to connect to (Default: singapore)
-i IP, --ip=IP Local IP address (Default: 127.0.0.1)
-p PORT, --port=PORT Local port (Default: 8080)
-v, --version Show version
-h, --help Show help
Advanced Options
--log-level=LEVEL Log level (Default: info)
--log-format=FORMAT Log format (Default: simple)
--service-domain=DOMAIN Service to connect to (Default: snekway.com)
--service-port=PORT Service port to connect to (Default: 80)
Environment variables
LOG_LEVEL
Default: info
Levels: trace, debug, info, notice, warn, error, fatal, none
LOG_FORMAT
Default: simple
Formats: simple, expanded
SERVICE_DOMAIN
Default: snekway.com
SERVICE_PORT
Default: 80
Network
Region | Cloud | IP | Host |
---|---|---|---|
oregon | AWS | 18.236.103.138 | snek4 |
virginia | GCP | 35.245.40.106 | snek5 |
eemshaven | GCP | 34.91.35.26 | snek6 |
Mumbai | GCP | 35.244.51.207 | snek7 |
singapore | GCP | 34.87.82.40 | snek8 |
frankfurt | GCP | 34.89.138.230 | snek9 |
toronto | GCP | 34.135.37.16 | snek10 |
Roadmap
I have many ideas for how to improve Snekway, but the ones I have decided on will be on the 2023 roadmap