calendarwatch_frontend/docker/calendarwatch/docker-entrypoint.sh

#!/bin/sh
cd /home/calendarwatch

# use flasks own uwsgi server for debugging:
# export FLASK_APP=/home/calendarwatch/server.py
# python3 server.py


# the --lazy flag forks() a new instance of the server
# instead of forking from the parent and copying the same mysql
# connection. If you don't do that, then multiple forks will use
# the same connection at the same time, causing the server to throw
# a 'connection has gone away' error.
# more here: https://serverfault.com/questions/407612/error-2006-mysql-server-has-gone-away
uwsgi --ini wsgi.ini --lazy
echo "server has been started"
adds structure for virtual environment uwsgi and http communication - starts uwsgi and flask in virtual environment instead of docker - sets oauth2 https error to false (OAUTHLIB_INSECURE_TRANSPORT=1) - this setup works, but - moving it into docker - removing the venv - and allowing https connection internally? would be better 2020-05-10 20:31:42 +02:00			`#!/bin/sh`
			`cd /home/calendarwatch`
uwsgi initialization uses the --lazy flag, to prevent connection overload as described in https://serverfault.com/questions/407612/error-2006-mysql-server-has-gone-away the uwsgi server usually forks its workers from the parent, which already has a connection open to the mysql database. So the new child typically inherits the same connection. Should both workers use the same connection at the same time, the server connection throws a '2006, server has gone away error'. The flag --lazy creates fresh forks for each child, each creating a new connection. This prevents the overload and after testing, the '2006' error seems to not be reproduceable. 2020-08-17 13:21:33 +02:00
			`# use flasks own uwsgi server for debugging:`
			`# export FLASK_APP=/home/calendarwatch/server.py`
			`# python3 server.py`


			`# the --lazy flag forks() a new instance of the server`
			`# instead of forking from the parent and copying the same mysql`
			`# connection. If you don't do that, then multiple forks will use`
			`# the same connection at the same time, causing the server to throw`
			`# a 'connection has gone away' error.`
			`# more here: https://serverfault.com/questions/407612/error-2006-mysql-server-has-gone-away`
			`uwsgi --ini wsgi.ini --lazy`
updates color generation, tries fixing credentials bug - credentials still lost the refresh token after a certain event - this was now fixed by completely removing any saves past the first one - https://trello.com/c/iORYLYHl/44-1-check-on-credentials - Color Coding is now updated - fixed an incorrect color mapping in the colors.json - updates some calls to functions to correctly get the natural colors - the incorrect red -> yellow mapping might have to do with the previous credentials error 2020-05-17 22:59:12 +02:00			`echo "server has been started"`