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

Refactor/issue 464 sepreate env files by profile #465

Merged
merged 3 commits into from
Jan 19, 2023

Conversation

ChoHadam
Copy link
Member

@ChoHadam ChoHadam commented Jan 17, 2023

Why:

Closes #464

What's being changed:

  • Update workflow files.
    • Use SERVER_NAME to match NODE_ENV here with NODE_ENV injected by the ecosystem.
    • Upgrade verion of node 12 to 16. (It was already applied in deploy-development.yml and deploy-test.yml)

@ChoHadam ChoHadam self-assigned this Jan 17, 2023
@ChoHadam ChoHadam linked an issue Jan 17, 2023 that may be closed by this pull request
@ChoHadam ChoHadam requested a review from heesung6701 January 17, 2023 07:15
- name: Use Node.js ${{ matrix.node-version }}
uses: actions/setup-node@8c91899e586c5b171469028077307d293428b516 #v.3.5.1
with:
node-version: ${{ matrix.node-version }}
- run: cp ~/config-injection/ecosystem-${{ env.NODE_ENV }}.json ${{ env.PROJECT_PATH }}/ecosystem.json
- run: cp ~/config-injection/.env ${{ env.PROJECT_PATH }}/.env
- run: cp ~/config-injection/ecosystem-${{ env.SERVER_NAME }}.json ${{ env.PROJECT_PATH }}/ecosystem.json
Copy link
Member

Choose a reason for hiding this comment

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

NODE_ENV가 아닌 NODE_SERVER를 기준으로 사용한 이유가 있나요? Production과 production1,2는 같은 env를 공유하고있는데 현 방식이 되면 서버 종류만큼 env가 필요하게됩니다!

Copy link
Member Author

Choose a reason for hiding this comment

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

NODE_SERVER라는게 SERVER_NAME을 말씀하신거겠죠? 저희가 ecosystem은 서버 종류만큼 가지고 있어서 SERVER_NAME 적용한거고, .env는 NODE_ENV를 기준으로 가져오고 있습니다.

Copy link
Member

Choose a reason for hiding this comment

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

아 ecosystem이었군요! 제가 env로 잘못봤습니다!
NAME은 식별자보다 보여지는 이름에 더 가까운거 같아서 향후에 NAME대신 ID 혹은 PROFILE로 수정해도 좋을 거 같습니다!

Copy link
Member

@heesung6701 heesung6701 left a comment

Choose a reason for hiding this comment

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

승인했습니다! 고생했습니다!

@ChoHadam ChoHadam requested a review from heesung6701 January 17, 2023 10:46
@ChoHadam
Copy link
Member Author

@heesung6701 피드백 주신 부분 반영했습니다 :)

Copy link
Member

@heesung6701 heesung6701 left a comment

Choose a reason for hiding this comment

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

LGTM :)

@ChoHadam ChoHadam merged commit 381fe47 into dev Jan 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Refactoring] Separate .env files by profile
2 participants