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
Select server config at runtime #963
Select server config at runtime #963
Changes from all commits
2f602a0
3289578
6bb76a2
58ecbea
6f918ce
f54d05b
07e48a0
3d1d602
52f80e8
737d1bb
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.
so now
server_config.json.default
file is no longer being used? Why I don't see it being deleted from the codebase?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.
It's there for the convenience of developers. I can remove it or rename it to
server_config.json.develop
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.
How is it convenient? The purpose of this file was to contain default value of
server_config.json
. We needed this whole process of config file deployment in order not to haveserver_config.json
in our git, but have it on runtime.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.
As a developer, doing
cp server_config.json.default server_config.json
in a new development environment is less error prone than editing the file by hand.Default for whom? Naming it something like
.develop
or.standard
is more useful thandefault
.That functionality still works. It's just using
server_config.json.standard
by default if the specifiedserver_config.json
doesn't exist.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.
How it worked before was that
server_config.json
was automatically created, which is even less error prone.Then we're back at square one: why do we need
server_config.json.default
? I think the downside of using standard config for development is that in our statistics we won't be able to distinguish our own monkey usage from client monkey usage, but that doesn't sound like a big problem. If we think this is a problem, we need our codebase to use develop config by default and change this behavior to "use standard instead" during release process. To phrase it differently, we want to use develop by default and change it to whatever as part of our release process.