For the second approach, we can remove the condition to detect whether the app is in a production environment. Both of these approaches would be closer to the application level rather than involving external factors such as remapping ports using ssh.
The first approach is available in #13, we can talk about this. Thanks!
When we test in our local environments, we needed map port 80 on our machines to listen to port 3001, specified in README.md
$ sudo ssh -N -L 80:localhost:3001 `whoami`@localhost
This is needed for execution on our local machines for every time we turn our machines on and run the local app for the first time.
While remapping the ports via
ssh
works, I believe it will make more sense to proceed one of the following approaches:appConfig.js
callbackUrl: 'http://local.nypl.org:3001/callback' // For non-production environments
$ APP_ENV=development|qa CLIENT_SECRET=[client-secret] AWS_PROFILE=[aws-profile-name] OAUTH_CALLBACK_URL='http://local.nypl.org:3001/callback' npm start
For the second approach, we can remove the condition to detect whether the app is in a production environment. Both of these approaches would be closer to the application level rather than involving external factors such as remapping ports using
ssh
.The first approach is available in #13, we can talk about this. Thanks!