Skip to content

Conversation

mdbecker
Copy link
Collaborator

Fixes #64

Michael Becker added 2 commits March 18, 2020 14:30
…ed in git now"

This reverts commit c724eb0.

This commit breaks heroku deploys because $PORT needs to come from the dyno env
@mdbecker mdbecker requested a review from MooseQuest March 18, 2020 18:35
@mdbecker mdbecker self-assigned this Mar 18, 2020
Copy link
Collaborator

@MooseQuest MooseQuest left a comment

Choose a reason for hiding this comment

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

This looks good. This should allow the app to launch. We can review other methods in the future. We plan to move to k8s soon, so this should hold over production for moment.

@MooseQuest MooseQuest merged commit 66f9269 into master Mar 18, 2020
@MooseQuest MooseQuest deleted the fix_heroku branch March 18, 2020 18:41
@themightychris
Copy link
Member

@mdbecker can you give the alternative fix I proposed over here a try? #64 (comment)

Even after we deploy to k8s, I think we still want to keep the codebase deployable to Heroku, and it will be a source of inconsistency to have two duplicative configuration paths

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

unable to connect heroku app to frontend router via new toml files.
3 participants