- #24 Bugfix AWS delete only checking the first instance
- Change retries to 1 and set a timeout of 10s on fetch_ip
- Rewrote the check_alive function to be much simpler, the fetch_ip check was not viable at 20+ proxies. It took too long.
- Updated ip_list not to return IP:s slated for destruction
- Added option to restart AWS proxies, much faster than destroy/create and fetches a new IP. Not supported for DO.
- Opened up port 22 on proxies for debugging, future enhancement is to only allow web control. (Use the EC2_INSTANCE_CONNECT filter for the service parameter to get the IP address ranges in the EC2 Instance Connect subset. )
- Enhanced status messages a bit in the check_alive for AWS
- Moved check_delete/stop to before provision so it removes and then immediately provisions a new one instead of waiting 20s for the next tick
- Changed the proxy software to tinyproxy directly on the image instead of using docker. Much faster deployment and less CPU intensive so should work better with t2.nano
- Updated the settings checks to compare true/false as a string since it seems to be what it is getting, earlier a value of False in the config would read as true.
- Updated environ get to match the doc (ie SCALING instead of SCALE)
- Added botocore to requirements.txt, which seemed to be missing.
@xanrag thank you for all these fixes.