-
Notifications
You must be signed in to change notification settings - Fork 5
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
Fix build and setup #83
base: main
Are you sure you want to change the base?
Conversation
@@ -14,8 +14,6 @@ ENV BUNDLE_JOBS 8 | |||
ENV APP_HOME /myapp | |||
|
|||
ARG RAILS_ENV=production | |||
ENV RAILS_ENV=$RAILS_ENV | |||
ENV RACK_ENV=$RAILS_ENV |
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.
arg
is only available during build, but having those two env
s here makes them permanent.
This can have an undesired effect in the test environment. In my testings, having those two lines make the test environment use the development database. Which is not a problem because everything runs inside a transaction but it is not ideal.
@parndt, please make sure you have both of them in fly ✌️
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.
Actually, I take it back. I don't think my test environment was using development database because of these two lines.
Yet, I don't think it is a good idea to have the two env
s because it makes them permanent.
To run the tests: | ||
|
||
docker compose run --rm app bundle exec rspec | ||
|
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.
Appreciate if anyone can review English and if it is easy to understand 🤗.
Hello @parndt 👋, have you had time to look at this? Let me know if you won't have time, I can ping someone else ;) |
sometime "soon"*! |
This PR:
README.md
using dockerI started fixing our build, but then I went down the rabbit hole fixing the docker setup as well. If needed let me know I can split this into two PRs.