Closed zakaf closed 6 years ago
This is critical as aws ec2 instance requires reboot every once in a while due to security update. Current reboot procedure(reboot + ssh + running 3 command) will always be slower than new reboot procedure to be implemented (reboot + start up servers automatically)
Done with webapp 6b5c0626479aae77c48363f4baba33ba75a0ba12 Done with webserver 161baa00ac573afa31d33efe0858782f29d4b493
Done with crawler 36a2d6467ce960455e588c86d6a58e7909125054
All 3 processes automatically gets available in less than 20 seconds after server reboot
sudo systemctl [start/stop/status] [kdhc-webapp/kdhc-webserver/kdhc-crawler] to check process status
After running reboot command through AWS console, kdhc is available in less than a minute (testing ~ 50 seconds)
Let all processes essential to KDHC, run right after reboot, instead of manually running 3 commands individually. (Probably using systemd)