pull_all_apps calls a "git status" and checks if the response contains "nothing to commit, working directory clean". However, it seems that at least some versions of git output the message "nothing to commit, working directory clean". This causes bench update to not work in systems where the output message uses "tree" instead of "directory". This update is to allow both strings to be used.
* [Fix] Do not validate certificates while downloading node bash script
* [Fix] New nodejs installation procedure
* [Fix] Updated message for node update to use official node package manager scripts
* [Fix] Add travis build status to repo page
* fixed a bug in nginx config
i found a bug when the user of the bench is currently using a dns-multitenant setup and he has multiple sites, and then he decides to switch to multiport setup, then all the sites present on the server get assigned the same port "80" and you can't change the port of any site due to the exception "Port 80 is being used by..."
so i fixed the bug by assigning a new port number that is not in use to every unassigned site, so afterwards the user can set his own custom port for each site without having to face this exception and failing at this task
* fixed a compile error
that's what knowing too much c-based languages doesn to you
* changed increment method
* added a better description for port conflic
if you are using port-based multi-tenant setup, i have found that if your ports are set in the site_config.py of your sites, or you set the port manually by using set-nginx-port command, and you have a port conflict between sites, the exception message raised is not be very helpful especially if you have many sites in your setup, so i added a list of ports that are conflicted and at what sites
and the behavior of default port assignment is changed as follows:
at first, the first site created gets port number 80, and every other site will get a new sequential port number, then, if a port is set manually that was assigned automatically, the manually set port number is applied and the old site moves to a new port
but the conflict message only displays if two ports where manually (or in the site_config) assigned to a site, and the message will display the site names
* added a message displaying the current port to site setup
added a new message that displays the mappings between sites and ports if port multi-tenant setup is used
* fixed security error in browsers
some browsers prevent low numbered ports from being used, so instead of continuously assigning ports from 80 onward, we start at 80 and then jump to 8000, and then continue from there
* fixed a problem with start port
apparently setting a site at port 8000 breaks nginx, so i changed it to 8001
* changed naming scheme to snake case
