eg, say I have php webserver at
php.dev.azk.io and i have sleep.php
<?php sleep(65);. Compare these two:
⟩ time curl -v http://php.dev.azk.io/sleep.php ... * Empty reply from server curl: (52) Empty reply from server Command exited with non-zero status 52 0.00user 0.00system 0:30.02elapsed
vs going to the container directly
⟩ time curl -v http://php.dev.azk.io:32791/sleep.php ... < HTTP/1.1 200 OK ... 0.00user 0.00system 1:05.00elapsed
azk shellbehaviour and changing the window size.
SIGWINCHto the process running in the shell
azk shell, and then resize the terminal window, process inside is not aware and even entering bash commands turns into a pain
azk shellcontainer cleanup not
yieldand instead let it fire in the background? It causes 0.5-1s delay when exiting shell while we wait for docker to clean the container, but from user perspective I don't think anyone cares as long as it gets cleaned up in the end?
yieldseems to cause no ill sideeffects and speeds up our staging scripts that do a series of
azk shellcommands one after another
sudo usermod -aG docker $(id -un)See more here: http://docs.azk.io/en/installation/linux.html
sudo chown -R `id -un`:`id -gn` .
connectivitynpm package is used, which in that version tries to connect to google.com:80. I don't understand why this check is needed?