You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The docker production build is served by nginx. The nginx configuration does not support ssl to serve the content via https. Also there is no way to add this functionality into the production build, e. g. change the nginx default.conf file.
There is some docs about how to create a (additional) proxy server to do the encryption. But running another http server just to add some common feature seems rather odd.
http should not be used to serve sensitive data, and therefore should not being used to serve OwnRecipes (and its login etc.). OwnRecipes should include a simple way to add ssl.
The text was updated successfully, but these errors were encountered:
The docker production build is served by nginx. The nginx configuration does not support ssl to serve the content via https. Also there is no way to add this functionality into the production build, e. g. change the nginx
default.conf
file.There is some docs about how to create a (additional) proxy server to do the encryption. But running another http server just to add some common feature seems rather odd.
http should not be used to serve sensitive data, and therefore should not being used to serve OwnRecipes (and its login etc.). OwnRecipes should include a simple way to add ssl.
The text was updated successfully, but these errors were encountered: