Re: Runtime values in sti-php ini templates

Hi Mateus, At this time each image kind of handles this differently, as best I can tell. For example, the JBoss EAP image will look for settings.xml in the code repository and substitute that instead of the built-in one (over-simplifying). The issue is how you would do this in some kind of

Re: Runtime values in sti-php ini templates

On Tue, Feb 2, 2016 at 9:51 PM, Ben Parees wrote: > > > On Tue, Feb 2, 2016 at 12:21 PM, Mateus Caruccio < > mateus.caruc...@getupcloud.com> wrote: > >> This could lead to an issue since most .ini files depend on some module >> to be available, newrelic.so in my case. Simply

Re: Runtime values in sti-php ini templates

Exactly. I'm going to send a PR today. Just need to test it here. Em 02/02/2016 05:39, "Honza Horak" escreveu: > It seems fine to me as well, we need to make the images extensible. > > I'd just like to make sure I understand the use case -- that would mean > you'd add a file

Re: Runtime values in sti-php ini templates

I think that sounds reasonable, i'd be inclined to accept it as a PR. Adding Honza since his team technically controls the PHP image now (5.6 anyway). On Mon, Feb 1, 2016 at 4:43 PM, Mateus Caruccio < mateus.caruc...@getupcloud.com> wrote: > Hi. > > I need to run newrelic on a php container.