… to upcoming/*

Added ability to use wss for ssl deployments (eg traefik/nginx proxy manager).

This change allows to monitor and send MQTT messages from/to the
AnkerMake M5C on the command line as well as observe the printer status
via the Web GUI.
It is also possible to send print jobs from your slicer to the printer
without using AnkerMake Slicer or Studio (see README.md).
Due to the M5's additional hardware (camera, light) still being expected
to exist, the Web GUI will continuously wait for a camera connection.
This should be fixed in the future.

Now the PPPP badge just shows the status of the PPPP connection, and
this also works for the AnkerMake M5C. The new VIDEO badge now has the
same behavior as the original PPPP badge in that it shows the status of
the video stream.

Implemented new command 'config login', which also supports
captcha queries, should they happen.

If there is already a valid ankerctl configuration and the user
just wants to re-login via 'config login' then the printer IP
addresses are restored to their original value if the server did
not provide those IP addresses (for me it never does).
Also, moved around some code parts.

This new form also supports captcha requests.
Also fixed is the behavior that loading/importing a new configuration
led to the printer IP addresses being cleared.

This affects both the CLI 'config show' as well as the 'Setup' tab of
the web interface.

For this the flag '--store' was added to 'pppp lan-search'.

This fixes issue Ankermgmt#152.

…rs. Added helper shell script for docker.

Changed docker import to accept a login.json in the currect directory if available.

Added stand-alone dockerfile for building runtime container.

Instead of copying the whole gcode file data and then splitting it into
32 KB chunks (2nd copy), use a generator function which emits the chunks
along with the current offset to be used in the AABB request.

Added pyinstaller packaging for windows users.
Updated requirements needed to run transwarp.

Seems to not work well to have them separated.

This does now work, but it raises a lot more exceptions than just AnkerCriticalError (KeyboardInterrupt & TypeError) - probably from separate threads

Restarting pppp will initiate new connection attempts. Will monitor this for a bit, a lot more graceful than a force shutdown

Removed these by mistake

Will leave this running for a while

Felt fitting to add this here - though I can change target to the main repo

Hopefully the last commit - has survived 3 lost connections so far. (The previous method had the service always running, which was stable but not realistic)

…le (by design)

Haven't had a single error message since updating requirements!

Without this, logging in was never an option (would crash on start)