Currently both ngs.simoc.space and beta.simoc.space point to the same server. The deployment is done assuming the server is accessible through beta.simoc.space only, and it creates a letsencrypt cert for it. While accessing it through ngs.simoc.space there is no SSL cert and the user sees a warning. This PR changes the SERVER_NAME var from beta.simoc.space to ngs.simoc.space, so that the generated cert will work for ngs.simoc.space. It will start failing for beta.simoc.space, but we can handle the warning better than our users can.
This is just a temporary workaround while we get around installing separate certs for both.
Currently both
ngs.simoc.space
andbeta.simoc.space
point to the same server. The deployment is done assuming the server is accessible throughbeta.simoc.space
only, and it creates a letsencrypt cert for it. While accessing it throughngs.simoc.space
there is no SSL cert and the user sees a warning. This PR changes theSERVER_NAME
var frombeta.simoc.space
tongs.simoc.space
, so that the generated cert will work forngs.simoc.space
. It will start failing forbeta.simoc.space
, but we can handle the warning better than our users can.This is just a temporary workaround while we get around installing separate certs for both.