INSTALACJA na "czystym" systemie DEBIAN 8.10 (jessie), na serwerze VPS, w wersji:
Linux supla 3.16.0-4-amd64 #1 SMP Debian 3.16.43-2+deb8u3 (2017-08-15) x86_64 GNU/Linux
---------------------------------------------------------------------
apt-get install curl
apt-get -y install git
curl -sSL
https://get.docker.com | sh
curl -L
https://github.com/docker/compose/relea ... ose-`uname -s`-`uname -m` -o /usr/local/bin/docker-compose
git clone
https://github.com/SUPLA/supla-docker.git
cd supla-docker/cloud && wget
https://temp.fracz.com/supla-cloud-v2.1.5.tar.gz && cd ../..
apt-get install docker-ce=17.10.0~ce-0~debian
./supla-docker/supla.sh start
Z wstępnego testu wydaje się, że system supla zainstalował się poprawnie choć w logu (poniżej) są jakieś błędy.
---------------------------------------------------------------------
Log (docker logs --tail=50 supla-server):
2017-12-13 07:00:26,152 CRIT Supervisor running as root (no user in config file)
2017-12-13 07:00:26,175 INFO supervisord started with pid 1
2017-12-13 07:00:27,177 INFO spawned: 'supla-scheduler' with pid 7
2017-12-13 07:00:27,179 INFO spawned: 'supla-server' with pid 8
INFO[1513148427.199632] Scheduler version 1.0
INFO[1513148427.200268] Server version 1.8.5 [Protocol v8]
INFO[1513148427.200564] Started at Wed Dec 13 07:00:27 2017
INFO[1513148427.200943] Started at Wed Dec 13 07:00:27 2017
ERR[1513148427.228055] MySQL - Failed to connect to database.
ERR[1513148427.228559] MySQL - Failed to connect to database.
2017-12-13 07:00:28,229 INFO success: supla-scheduler entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-12-13 07:00:28,229 INFO success: supla-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
ERR[1513148428.229678] MySQL - Failed to connect to database.
ERR[1513148429.231235] MySQL - Failed to connect to database.
ERR[1513148430.232378] MySQL - Failed to connect to database.
ERR[1513148431.233579] MySQL - Failed to connect to database.
ERR[1513148432.235078] MySQL - Failed to connect to database.
ERR[1513148433.236176] MySQL - Failed to connect to database.
ERR[1513148434.238008] MySQL - Failed to connect to database.
ERR[1513148435.239899] MySQL - Failed to connect to database.
ERR[1513148436.241623] MySQL - Failed to connect to database.
ERR[1513148437.243644] MySQL - Failed to connect to database.
ERR[1513148438.245606] MySQL - Failed to connect to database.
ERR[1513148439.247298] MySQL - Failed to connect to database.
ERR[1513148440.250313] MySQL - Failed to connect to database.
ERR[1513148441.251478] MySQL - Failed to connect to database.
ERR[1513148442.253257] MySQL - Failed to connect to database.
ERR[1513148443.255284] MySQL - Failed to connect to database.
ERR[1513148444.256923] MySQL - Failed to connect to database.
ERR[1513148445.262575] MySQL - stmt prepare error - Table 'supla.supla_scheduled_executions' doesn't exist
ERR[1513148445.263936] MySQL - stmt prepare error - Table 'supla.supla_scheduled_executions' doesn't exist
ERR[1513148445.264388] MySQL - stmt prepare error - Table 'supla.supla_scheduled_executions' doesn't exist
ERR[1513148446.266910] MySQL - stmt prepare error - Table 'supla.supla_scheduled_executions' doesn't exist
ERR[1513148447.269815] MySQL - stmt prepare error - Table 'supla.supla_scheduled_executions' doesn't exist
ERR[1513148448.272205] MySQL - stmt prepare error - Table 'supla.supla_scheduled_executions' doesn't exist
ERR[1513148449.275400] MySQL - stmt prepare error - Table 'supla.supla_scheduled_executions' doesn't exist
ERR[1513148450.278173] MySQL - stmt prepare error - Table 'supla.supla_scheduled_executions' doesn't exist
ERR[1513148451.280013] MySQL - stmt prepare error - Table 'supla.supla_scheduled_executions' doesn't exist
ERR[1513148452.282683] MySQL - stmt prepare error - Table 'supla.supla_scheduled_executions' doesn't exist
---------------------------------------------------------------------
Uwagi:
1. Po zalogowaniu sie do serwera nie wiem czemu w oknach supla-dev i supla-client jako "Adres serwera" widzę "supla.dev" zamiast
mojegu adresu supla.djack.ovh
2. Jeżeli opcja "Rejestracja klientów" jest wyłączona, to rozumiem, że na głównej stronie serwisu nie powinno być pola "Utwórz konto".
Może powinna być opcja konfiguracji supla-server: private / public
3. Smartfon został zarejestrowany
To na razie tyle z testów.
Jacek