Version 0.2

• API keys are now fully supported. Pass --bytemark-token <api keyincluding the 'apikey.' prefix> to use them. API keys can be retrofit to an existing machine by editing the config.json for that machine and setting Token: to the full api key including the 'apikey.' prefix.
• --bytemark-cluster flag was added to allow staff to use docker-machine-driver-bytemark in bytemark's test environments
• When --debug is passed to docker-machine, docker-machine-driver-bytemark now logs all HTTP requests it makes.

Initial release!

This is a first version of docker-machine-driver-bytemark!

As with all docker-machine drivers, install the docker-machine-driver-bytemark binary from the tar.gz or the exe from the zip into somewhere in your PATH environment variable. and then run docker-machine as usual. See the readme for more usage examples!

It's not completely battle-tested yet, but it seems to work in general. If you're creating a docker-machine with a debian-based OS (the default) then please make sure to set --engine-storage-driver overlay2. YMMV with other OSes - we haven't tested them.

API keys (auth tokens with limited access that don't expire / have configurable expiry) are coming soon - so don't go jumping in and trying to autoscale gitlab-runners just yet 😀