mongodb-container
mongodb-container copied to clipboard
Timezone for container - petset
The default timezone is utc. Some customers need to have there local timezone. It would be nice to be able to set the timezone at the creation time
Can one of the admins verify this patch?
Can one of the admins verify this patch?
Can one of the admins verify this patch?
Can one of the admins verify this patch?
Can one of the admins verify this patch?
[test][test-openshift]
There is missing setting TZ variable inside container. @git001 Please add.
{
"name": "TZ",
"value": "${TIMEZONE}"
}
done
Thanks for your contribution.
@git001 I hope last two things, please rebase to latest master (now PR can't be merged) and and empty line before TIMEZONE variable in mongodb-petset-persistent.yaml . Thanks, I'll merge it then.
[test][test-openshift]
ping
sorry but again I fail on git handling.
I always edit over the GUI and when the PR is commented I never come to a good result with the git commands.
Isn't is possible to use squashed merge? https://help.github.com/articles/about-pull-request-merges/#squash-and-merge-your-pull-request-commits
I thin due to the limitation of the GUI I will stop to contribute, just because it makes me so much headache to make it in the right way.
If the squash-and-merge way is not possible then just throw the PR.
@git001 It is possible to use "squash merge". But this won't solve file conflicts (so it is not possible).
I thin due to the limitation of the GUI I will stop to contribute, just because it makes me so much headache to make it in the right way.
With command line it can be done:
- Add
upstreamremote - https://help.github.com/articles/configuring-a-remote-for-a-fork/ git checkout <your branch>andgit rebase upstream/master- In file
examples/petset/mongodb-petset-persistent.yamlis conflict, so automatic rebase is not possible (git rebasecommand will tell). So manual edit of conflict file is required (to contain both - your and upstream changes), thengit add <updated conflict file>andgit rebase --continue. - Force push to PR branch.
Or should I create a new PR?
Can one of the admins verify this patch?
Can one of the admins verify this patch?
Can one of the admins verify this patch?
Can one of the admins verify this patch?
Can one of the admins verify this patch?
Can one of the admins verify this patch?
Can one of the admins verify this patch?
mongodb container is not maintained any more in this org. closing.