On Sun, Nov 6, 2016 at 7:48 AM, Shlomi Zadok wrote:
> Hey list,
> A while back I have created a Foreman docker-compose repo [1], that runs
> Foreman under docker-compose, separated to several containers (Foreman /
> Proxy / DB / HAproxy).
> Recent contributions by Ohad and
- Original Message -
> From: "Dominic Cleal"
> To: foreman-dev@googlegroups.com
> Sent: Tuesday, November 8, 2016 5:42:04 AM
> Subject: Re: Creating a plugin-for-tests (was [foreman-dev] Plugin test
> failures)
>
> On 07/11/16 15:39, Stephen Benjamin wrote:
> > The
I opened a PR in foreman-infra that removes ruby 1.9.3 from test
matrix: https://github.com/theforeman/foreman-infra/pull/256.
-d
On Monday, November 7, 2016 at 11:41:13 AM UTC, Dmitri Dolguikh wrote:
>
> Awhile ago when we announced end of support for ruby 1.8.7 for
> smart-proxy, we also
Hello,
Previously, the alert() helper would consider any text passed to it as
html_safe. This led to a CVE, where user provided data was passed into the
text field of the alert, leading to a possible stored XSS (cross site
scripting) vulnerability.
https://github.com/theforeman/foreman/pull/3996
On Sun, Nov 06, 2016 at 07:51:16AM -0800, Jo De Troy wrote:
> I'm pretty new to foreman and the smart-proxies.
> I was wondering if the following is possible or if this would need more
> development work:
> * when creating a new VM just specify the network the VM needs to be in
> and Foreman
Hello,
I'm pretty new to foreman and the smart-proxies.
I was wondering if the following is possible or if this would need more
development work:
* when creating a new VM just specify the network the VM needs to be in
and Foreman would contact Infoblox to get the next available ip in this
On 07/11/16 15:39, Stephen Benjamin wrote:
> The wiki says that public methods will be deprecated and given a chance
> to adjust our code in a reasonable time where possible:
>
> "Foreman will always strive to make no incompatible changes in a minor
> release, but be prepared
> to make