wordpress

deprecated
Puppet module for wordpress

Example42

example42

10,022 downloads

7,829 latest version

4.0 quality score

Version information

  • 2.0.8 (latest)
  • 2.0.7
  • 2.0.6
released Jun 30th 2015
This module has been deprecated by its author since Oct 28th 2019.

The reason given was: No longer maintained

The author has suggested hunner-wordpress as its replacement.

Start using this module

Documentation

example42/wordpress — version 2.0.8 Jun 30th 2015

Puppet module: wordpress

DEPRECATION NOTICE

This module is no more actively maintained and will hardly be updated.

Please find an alternative module from other authors or consider Tiny Puppet as replacement.

If you want to maintain this module, contact Alessandro Franceschi

This is a Puppet wordpress module from the second generation of Example42 Puppet Modules.

Made by Alessandro Franceschi / Lab42

Official site: http://www.example42.com

Official git repository: http://github.com/example42/puppet-wordpress

Released under the terms of Apache 2 License.

This module requires functions provided by the Example42 Puppi module.

For detailed info about the logic and usage patterns of Example42 modules read README.usage on Example42 main modules set.

USAGE - Basic management

  • Install wordpress using your distro package, if available

      class { "wordpress": }
    
  • Install the latest wordpress version from upstream site

      class { "wordpress":
        install             => "source",
      }
    
  • Install the latest wordpress version from upstream site using puppi. You will have a 'puppi deploy wordpress' to deploy and update wordpress.

      class { "wordpress":
        install             => "puppi",
      }
    
  • Install source from a custom url to a custom install_destination path. The following parameters apply both for "source" and "puppi" install methods. Puppi method may be used to manage deployment updates (given the $install_source is updated). By default install_source is set to upstream developer and install_destination to Web (App) server document root Pre and post installation commands may be already defined (check wordpress/manifests/params.pp) override them only if needed. Url_check and url_pattern are used for application checks, if monitor is enabled. Override only if needed.

      class { "wordpress":
        install             => "source",
        install_source      => "http://deploy.example42.com/wordpress/wordpress.tar.gz",
      }
    
  • Remove wordpress

      class { "wordpress":
        absent => true
      }
    
  • Enable auditing without without making changes on existing wordpress configuration files

      class { "wordpress":
        audit_only => true
      }
    

USAGE - Overrides and Customizations

  • Use custom sources for main config file

      class { "wordpress":
        source => [ "puppet:///modules/lab42/wordpress/wp-config.php-${hostname}" , "puppet:///modules/lab42/wordpress/wp-config.php" ], 
      }
    
  • Use custom source directory for the whole configuration dir

      class { "wordpress":
        source_dir       => "puppet:///modules/lab42/wordpress/conf/",
        source_dir_purge => false, # Set to true to purge any existing file not present in $source_dir
      }
    
  • Use custom template for main config file

      class { "wordpress":
        template => "example42/wordpress/wp-config.php.erb",      
      }
    
  • Automaticallly include a custom subclass

      class { "wordpress":
        my_class => 'wordpress::example42',
      }
    
  • Use custom options with existing template. Full list includes: DB_CHARSET, DB_COLLATE, AUTH_KEY, SECURE_AUTH_KEY, LOGGED_IN_KEY, NONCE_KEY, AUTH_SALT, SECURE_AUTH_SALT, LOGGED_IN_SALT, NONCE_SALT, table_prefix, WPLANG, WP_DEBUG

      class { "wordpress":
        options => {
          'DB_CHARSET' => 'utf8',
          'DB_COLLATE' => 'utf8_general_ci',
          'WP_DEBUG'   => 'true',
        },
      }
    

USAGE - Example42 extensions management

  • Activate puppi (recommended, but disabled by default) Note that this option requires the usage of Example42 puppi module

      class { "wordpress": 
        puppi    => true,
      }
    
  • Activate puppi and use a custom puppi_helper template (to be provided separately with a puppi::helper define ) to customize the output of puppi commands

      class { "wordpress":
        puppi        => true,
        puppi_helper => "myhelper", 
      }
    
  • Activate automatic monitoring (recommended, but disabled by default) This option requires the usage of Example42 monitor and relevant monitor tools modules

      class { "wordpress":
        monitor      => true,
        monitor_tool => [ "nagios" , "puppi" ],
      }
    

Build Status