-
Notifications
You must be signed in to change notification settings - Fork 159
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
add .env for a straightforward dev deployment #354
Conversation
👷 Deploy Preview for amazing-pothos-a3bca0 processing.
|
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## main #354 +/- ##
===========================================
- Coverage 91.28% 79.53% -11.75%
===========================================
Files 48 48
Lines 1686 1686
===========================================
- Hits 1539 1341 -198
- Misses 147 345 +198 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for addressing the feedback, @CorsettiS!
## Description In the process of setting up the dev environment, an empty .env file is requested to build the image. Since there is no visible impact on having it not having it, for consistency it is better to remove this not used dependency from the docker compose yml file. ## Related Issue(s) somehow related to #342 ## Breaking Change? No major changes are going to happen ## Checklist - [ ] I have made corresponding changes to the documentation (if required) - [ ] I have added tests that prove my fix is effective or that my feature works --------- Co-authored-by: giovanni.corsetti <[email protected]> Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: Harel Shein <[email protected]>
Description
In the process of setting up the dev environment, an empty .env file is requested to build the image. Since there is no visible impact on having it not having it, for consistency it is better to remove this not used dependency from the docker compose yml file.
Related Issue(s)
somehow related to #342
Breaking Change?
No major changes are going to happen
Checklist