Set redirectUrl for production; rely on NODE_CONFIG_ENV being set earlier (#2656)

This commit is contained in:
Paul Melnikow
2019-01-06 12:56:26 -05:00
committed by GitHub
parent bc0be4f619
commit 47bb03572b
2 changed files with 3 additions and 2 deletions

View File

@@ -28,9 +28,8 @@ prepare-server-deploy: website
cp -r build ${SERVER_TMP}
git -C ${SERVER_TMP} add -f build/
git -C ${SERVER_TMP} commit --no-verify -m '[DEPLOY] Add frontend for debugging'
echo 'NODE_CONFIG_ENV=shields-io-production' > ${SERVER_TMP}/.env
cp config/local-shields-io-production.yml ${SERVER_TMP}/config/
git -C ${SERVER_TMP} add -f .env config/local-shields-io-production.yml
git -C ${SERVER_TMP} add -f config/local-shields-io-production.yml
git -C ${SERVER_TMP} commit --no-verify -m '[DEPLOY] MUST NOT BE ON GITHUB'
clean-server-deploy:

View File

@@ -9,6 +9,8 @@ public:
cors:
allowedOrigin: ['http://shields.io', 'https://shields.io']
redirectUrl: 'https://shields.io/'
private:
# These are not really private; they should be moved to `public`.
shields_ips: ['192.99.59.72', '51.254.114.150', '149.56.96.133']