Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

create workflows for deploying front + back end #472

Merged
merged 3 commits into from
Oct 18, 2023

Conversation

mattdelsordo
Copy link
Contributor

@mattdelsordo mattdelsordo commented Sep 25, 2023

I followed the example at https://github.com/nerc-project/simple-node-app and think this should "just work". I ran NERC's scripts to set the required secrets on the github project, but I'm not sure where to check whether that worked.

Resolves #483

@mattdelsordo mattdelsordo added the enhancement New feature or request label Sep 25, 2023
@mattdelsordo mattdelsordo force-pushed the mattdelsordo/deploy-workflow branch from 8933d1a to da3a712 Compare September 25, 2023 01:16
@mattdelsordo
Copy link
Contributor Author

Forgot about the environment variables - will be adding that in.

@mattdelsordo mattdelsordo force-pushed the mattdelsordo/deploy-workflow branch from da3a712 to a08028e Compare September 26, 2023 22:08
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Unfortunately I had to revert this change here because it borked the tests. The problem solved still exists so we're going to have to address it anyway: #469

context: frontend/front
port: 8080
secrets:
build-args: |
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Not 100% positive all of the "normal" secrets are going to get passed like I expect...

@mzagaja
Copy link
Member

mzagaja commented Sep 26, 2023

@mattdelsordo I see secrets at
image

@mzagaja
Copy link
Member

mzagaja commented Sep 26, 2023

@mattdelsordo Can you remove the now to be unused bits in https://github.com/codeforboston/urban-league-heat-pump-accelerator/blob/main/.github/workflows/test.yml so that we aren't building images for AWS anymore as a part of the workflow.

@mattdelsordo mattdelsordo force-pushed the mattdelsordo/deploy-workflow branch from d4193a9 to 2d1b463 Compare September 26, 2023 23:28
@mattdelsordo
Copy link
Contributor Author

@mzagaja would you be able to fix the back-end security check?

@mattdelsordo
Copy link
Contributor Author

@mzagaja does this look good to merge?

@mzagaja
Copy link
Member

mzagaja commented Oct 16, 2023

@mattdelsordo I was hoping to dig into this and test it today but the MassOpenCloud server space is having an issue. Hopefully it resolves soon. Meanwhile I will review from a code perspective.

Copy link
Member

@mzagaja mzagaja left a comment

Choose a reason for hiding this comment

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

Just a couple minior changes for now. Then let's merge and test this, hopefully Mass Open Cloud will be up tomorrow.


env:
REACT_APP_PUBLIC_SURVEY_ENABLED: 'false'
REACT_APP_API_URL: https://bhpa-backend-boston-heat-pump-accelerator-dbab1b.apps.shift.nerc.mghpcc.org
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
REACT_APP_API_URL: https://bhpa-backend-boston-heat-pump-accelerator-dbab1b.apps.shift.nerc.mghpcc.org
REACT_APP_API_URL: https://api.bostonhpa.org

Comment on lines 6 to 8
push:
# Edit to the branch(es) you want to build and deploy on each push.
branches: ['main']
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
push:
# Edit to the branch(es) you want to build and deploy on each push.
branches: ['main']
release:
types: [published]

@mzagaja
Copy link
Member

mzagaja commented Oct 16, 2023

@mattdelsordo Do you mind 👀 on the merge conflicts for the front end stuff here and then we can try taking this for a spin when MOC is ready?

@mattdelsordo mattdelsordo force-pushed the mattdelsordo/deploy-workflow branch from cf55c47 to 36dbdff Compare October 16, 2023 21:09
@mzagaja mzagaja self-requested a review October 18, 2023 00:45
Copy link
Member

@mzagaja mzagaja left a comment

Choose a reason for hiding this comment

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

🚀

@mattdelsordo
Copy link
Contributor Author

does 🚀 mean I should merge this or

@lhuhmann
Copy link
Contributor

does 🚀 mean I should merge this or

Yes, merge it! We looked at this together tonight, but didn't want to merge it without you.

@mattdelsordo mattdelsordo merged commit 5bc251a into main Oct 18, 2023
4 checks passed
@mikelynch mikelynch deleted the mattdelsordo/deploy-workflow branch October 23, 2023 00:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

Successfully merging this pull request may close these issues.

Github workflow to deploy front + back ends
3 participants