Re: [foreman-dev] Discourse summary week 2 (ish)

2017-11-15 Thread Sebastian Gräßl
I am one of the (silent) +1 voices Greg mentioned. Discourse would be a very welcomed move for me, there are a number of reasons, which Greg already mentioned as well. For me the one key reason is the possibility to have multiple categories to have discussions and share information in a

[foreman-dev] Re: Foreman core nightly is currently broken

2017-09-05 Thread Sebastian Gräßl
There is now another approach to fix this by using a plain Object instead of a Map[1]. This won't require any additional dependencies to be added. [1] https://github.com/theforeman/foreman/pull/4811 On Tuesday, September 5, 2017 at 9:27:13 AM UTC+2, ohadlevy wrote: > > Hi, > > Following up on

Re: [foreman-dev] Re: [RFC] HTTP proxy for requests

2017-06-22 Thread Sebastian Gräßl
r. Why not simply add a new setting in > Foreman? > > -- > Marek > > On středa 21. června 2017 16:28:38 CEST Sebastian Gräßl wrote: > > The biggest part of this all is actually ensuring that all requests made > by > > the application are actually going through the

Re: [foreman-dev] Re: [RFC] HTTP proxy for requests

2017-06-21 Thread Sebastian Gräßl
> > > > > I'd like to echo what tom said, we've had many users that want to > access > > > content externally through a proxy and internally (where the proxy is > > > not controlled by them and does not properly proxy internal requests). > >

[foreman-dev] [RFC] HTTP proxy for requests

2017-04-20 Thread Sebastian Gräßl
Hej, at the moment there is a PR[1] open on foreman-docker to set a HTTP proxy for requests to registries. The PR allows to set a HTTP proxy on the HTTP client, in this case deep down Excon, only for registry requests. A HTTP proxy won't be set on requests if a `HTTP_PROXY` environment