Skip to content
This repository has been archived by the owner on May 22, 2024. It is now read-only.

Fix Default Port Value #202

Merged
merged 12 commits into from
Nov 13, 2018
Merged

Fix Default Port Value #202

merged 12 commits into from
Nov 13, 2018

Conversation

emilyrohrbough
Copy link
Contributor

Summary

Default port value is returning NaN.

Dockerfile Outdated
@@ -2,4 +2,4 @@
FROM cerner/terra-node

# run the server
CMD ["npm", "run", "start"]
CMD ["npm", "run", "start", "--", "--port", "8080"]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is temporary until we get a clean release right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes should be. @ryanthemanuel When do we push the 'latest' tagged docker image?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Though, i'd be remiss if i didn't point out that if we were testing against this version and not the previously released version, this issue wouldn't have been released.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also i'm pretty sure my previous comment was wrong. Please disregard. :)

Rohrbough,Emily added 2 commits November 12, 2018 14:13
@tbiethman
Copy link
Contributor

+1 for commit messages

@bjankord
Copy link
Contributor

Can we test this branch against terra-core?

@emilyrohrbough
Copy link
Contributor Author

@bjankord I have setup a test branch in terra-core. I have opened a dummy PR to validate the CI tests pass as expected, but I also need someone to pull the project and validate these commands:

  1. npm run start
  2. npm run start -- --port 9090
  3. npm run start-static
  4. npm run start-static -- --port 9090

Copy link
Contributor

@mjhenkes mjhenkes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 final changes

@terra-bot
Copy link

Warnings
⚠️

❗ Big PR. Consider breaking this into smaller PRs if applicaple

Generated by 🚫 dangerJS

@emilyrohrbough
Copy link
Contributor Author

After spending way too log going down a lovely rabbit hole with @mjhenkes , it was discovered har-validator project released v5.1.3 three days ago and must have corrupted/removed the v5.1.2 version. This is why the builds were continuously failing on the install step.

screen shot 2018-11-13 at 10 01 53 am

Removing the package-lock did the trick to clean this up.

@emilyrohrbough emilyrohrbough merged commit 2bb09df into master Nov 13, 2018
@emilyrohrbough emilyrohrbough deleted the fix-default-port branch November 13, 2018 16:21
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants