Jon Trossbach

I just got done deploying Postgres13 from these changes as a back end to my Discourse instance. They worked for me and allowed me to automate the processes I have...

Thanks @pvalena! I amended my interpretation of the changes you recommended to this commit. Let me know if you have anymore feedback.

[test]

My apologies, I didn't realize this was installing an unsupported version of Bundler. I guess I don't know what Discourse is doing when they're gemlocking ahead of what most people...

Thank you for the reply Pavel. I found an issue from the rubygems repo discussing just this topic a number of years ago and it appears they want people using...

I appreciate your time, Pavel, but I am not sure your interpretation of that issue is right given this quote from one of the developers, git handle name: segiddins. ```"This...

@jasonbrooks situation on OpenShift can be recreated by deploying [this Discourse OpenShift instance](https://github.com/jontrossbach/openshift-discourse) and running through the two step build (s2i then Discourse) on the main branch with a changed...

We are trying to take directly from the Discourse official source releases and patches to maintain an up-to-date managed OpenShift Discourse instance for upstream communities so we are pulling directly...

Steps to reproduce from sclorg/ruby-ex: ``` $ oc new-project abigail-sclorg-ruby-ex-test $ oc new-app openshift/ruby:2.6-ubi8~https://github.com/jontrossbach/ruby-ex ``` This was all I did to my ruby-ex example: https://github.com/jontrossbach/ruby-ex/blob/master/Gemfile.lock#L16 This was the build result:...

Oh but interestingly 2.7 is building with just a warning... now I'm stumped. ``` $ oc new-project abigail-sclorg-ruby-ex-test $ oc new-app openshift/ruby:2.6-ubi8~https://github.com/jontrossbach/ruby-ex ``` The build log was: ``` Cloning "https://github.com/jontrossbach/ruby-ex"...