Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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/review setup (#52) #54
base: main
Are you sure you want to change the base?
Fix/review setup (#52) #54
Changes from 3 commits
c779cc6
8350f87
367178f
dfef10b
0448392
e47af6b
82de2a9
2523780
79ad499
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
This is a slight thing, but in
redmine_gtt
plugin'sREADME.md
, we usenpx webpack
, but is it better to changeyarn webpack
in theREADME.md
side ?https://github.com/gtt-project/redmine_gtt#installation
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.
@dkastl (CC: @smellman)
In my opinion,
puma_worker_killer
is for production environment, but shall we assume thisdocker-gtt
setup forproduction
environment (not fordevelopment
environment) ?Also,
lograge
is for changing rails log as JSON format which is convenience on AWS ECS log and CloudWatch, but shall we assume AWS as first deployment priority ?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.
Not sure ... but we actually run it
--without test development
and withproduction
environment, so I wouldn't say it's a problem to keep it.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.
@dkastl
Okay, sure at this moment...
By the way, I found the way to support both (
production
andtest development
) env in another project, so it can be solved.For debugging purpose, multiple workers (=3) and
puma_worker_killer
is quite annoying for me, so personally configurable this part with additional environment variables will be the best way.How about this ?
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.
By the way,
mailcatcher
is used indocker-compose.yml
, so it's a kind of halfproduction
and halfdevelopment
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.
Well, don't know very much about these details. Could you just make a change that works good for development and push it to this branch?
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.
Do you mean only the following part ?
If so, it's okay for me.
But if it's also gem dependencies (
puma
,puma_worker_killer
andlograge
), we need to decide something this project's scope ,etc ?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.
I think the question is, what the "target audience" of this Docker setup is. I think your perspective is the developer point of view. But there could be also the point of view of someone, who wants to use this to deploy and use the service. For example some SMASH user.
Of course it's best to support both use cases, for example with ENV settings. But we don't need to have this all ready with the first PR.
Maybe the non-developer use case should be priority, because a developer can also adjust the Docker setup. What do you think?
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.
@dkastl (CC: @smellman)
Well, after I read the following Redmine Email Configuration again, I prefer to keep this
SMTP_AUTHENTICATION
configurable.https://www.redmine.org/projects/redmine/wiki/EmailConfiguration
Is there some reason to drop this configuration ?