Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Creating new project specific pool does not refresh PHP-FPM #14

boztek opened this Issue Mar 20, 2013 · 3 comments


None yet
2 participants

boztek commented Mar 20, 2013

I can happily use either boxen::project and manually declare a project specific pool or use php::project - both with a custom nginx template for some app specifics.

In either case I seem to have to kill php-fpm and rerun boxen for everything to work.


mattheath commented Mar 20, 2013

Yeah this is similar to #1. It's caused by the php::fpm::pool class requiring the php::fpm class which includes the service. As the entire class is required, the service can't be notified - it creates a dependency loop.

I think I've worked out a fix which requires changing part of the dependency chain, will have another look later today. For the moment you can use the following to slightly speed this up, rather than having to re-run boxen!

boxen --disable-services
boxen --enable-services

mattheath commented Mar 20, 2013

I've merged this, and retagged as 0.4.2. Pool config files now notify the FPM service for the PHP version, which should trigger a refresh of the service. @boztek could you let me know if it works for you?


mattheath commented May 28, 2013

Closing this as I'm fairly certain it's fixed - let me know if this is still an issue.

@mattheath mattheath closed this May 28, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment