CODEWITHSUNDEEP
phpapache.htaccessconfiguration
Nick
Nick

Reputation: 2913

How to manage different php.ini settings in production and development?

Is there a best practice for managing php.ini configurations from development to production? Obviously it can be done manually, but that is prone to human error. I'd like to try and have the production file in version control and then possibly modify the development version automatically. Thoughts or ideas i've had which i dont know if they are feasible:

  1. php.ini includes - just include the dev settings at the end of the file?
  2. conditional loads from apache conf?
  3. write a script that when php.ini changes, a dynamic version of phpdev.ini gets generated - (i know this can be done)
  4. use runtime php settings for display errors - i think this has limitations because if the script has fatal errors, then it wont run the runtime setting.
  5. backup plan - keep the production version in SC, and manually change phpdev.ini as needed as needed. Then if manual mistakes are made they are done at the development level.

Upvotes: 2

Views: 2858

Answers (2)

Kzqai
Kzqai

Reputation: 23102

I don't know exactly if this is what you're looking for, but personally I like to perform all non-security-necessary php.ini modifications via the apache virtualhost settings, e.g. a development virtualhost:

    ServerName sb.local
    ServerAlias sb.local
    DocumentRoot /srv/some-site

    php_value session.cookie_domain "sb.local"
php_value date.timezone "America/New_York"
php_value mbstring.func_overload 7
php_value default_charset "utf-8"
AddDefaultCharset utf-8 

php_value session.gc_maxlifetime "990000"
php_value error_reporting 30711
# 30711 = E_ALL ^ E_NOTICE
php_value display_errors "On"
php_value display_startup_errors "On"
php_value log_errors "On"
php_value html_errors "On"

etc

Upvotes: 0

Theodore R. Smith
Theodore R. Smith

Reputation: 23259

  1. Store your ini in your source code repository in different directories named after their environments: environments/{dev,qa,staging,prod}/php.ini
  2. On each environment, do this: rm /etc/php.ini; ln -s /var/www/site/environments/prod/php.ini /etc/php.ini

This way, you get the benefits of revision control and don't necessarily have to edit each manually.

Upvotes: 2

Related Questions