Make database connections configurable by environment variables #768

병합
KitaitiMakoto db-conns-conf 에서 master 로 4 commits 를 머지했습니다 4 년 전
KitaitiMakoto 코멘트됨, 4 년 전 (Migrated from github.com)

so that we can tune performance.

so that we can tune performance.
codecov[bot] 코멘트됨, 4 년 전 (Migrated from github.com)

Codecov Report

Merging #768 into master will decrease coverage by 0.03%.
The diff coverage is 18.18%.

@@            Coverage Diff             @@
##           master     #768      +/-   ##
==========================================
- Coverage   38.99%   38.96%   -0.04%     
==========================================
  Files          73       73              
  Lines        9721     9729       +8     
  Branches     2226     2227       +1     
==========================================
  Hits         3791     3791              
- Misses       4878     4885       +7     
- Partials     1052     1053       +1     
# [Codecov](https://codecov.io/gh/Plume-org/Plume/pull/768?src=pr&el=h1) Report > Merging [#768](https://codecov.io/gh/Plume-org/Plume/pull/768?src=pr&el=desc) into [master](https://codecov.io/gh/Plume-org/Plume/commit/180e34b07c014a3a37b2031cf0532ee17104f47b&el=desc) will **decrease** coverage by `0.03%`. > The diff coverage is `18.18%`. ```diff @@ Coverage Diff @@ ## master #768 +/- ## ========================================== - Coverage 38.99% 38.96% -0.04% ========================================== Files 73 73 Lines 9721 9729 +8 Branches 2226 2227 +1 ========================================== Hits 3791 3791 - Misses 4878 4885 +7 - Partials 1052 1053 +1 ```
elegaanz (Migrated from github.com) 검토됨 4 년 전
elegaanz (Migrated from github.com) left a comment

Nice! I just have a small question, but otherwise it seems good to merge. Thanks!

Nice! I just have a small question, but otherwise it seems good to merge. Thanks!
elegaanz (Migrated from github.com) 코멘트됨, 4 년 전

Is there a reason for panicking in one case and silently failing in the other?

Is there a reason for panicking in one case and silently failing in the other?
KitaitiMakoto (Migrated from github.com) 검토됨 4 년 전
KitaitiMakoto (Migrated from github.com) 코멘트됨, 4 년 전

Good catch! There's no reason why. I will rewrite this and push it.

Good catch! There's no reason why. I will rewrite this and push it.
KitaitiMakoto (Migrated from github.com) 검토됨 4 년 전
KitaitiMakoto (Migrated from github.com) 코멘트됨, 4 년 전

Done.

Done.
elegaanz (Migrated from github.com) 이 변경사항을 승인하였습니다. 4 년 전
elegaanz (Migrated from github.com) left a comment

Great!

Great!
KitaitiMakoto 코멘트됨, 4 년 전 (Migrated from github.com)

Thank you for the merge.

Thank you for the merge.

리뷰어

The pull request has been merged as 3be842c653.
You can also view command line instructions.

Step 1:

From your project repository, check out a new branch and test the changes.
git checkout -b db-conns-conf master
git pull origin db-conns-conf

Step 2:

Merge the changes and update on Forgejo.
git checkout master
git merge --no-ff db-conns-conf
git push origin master
로그인하여 이 대화에 참여
No reviewers
마일스톤 없음
담당자 없음
참여자 1명
알림
마감일
기한이 올바르지 않거나 범위를 벗어났습니다. 'yyyy-mm-dd'형식을 사용해주십시오.

마감일이 설정되지 않았습니다.

의존성

No dependencies set.

Reference: Plume/Plume#768
불러오는 중...
아직 콘텐츠가 없습니다.