Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: support from installing Wordpress from RPM #31

Open
djjudas21 opened this issue Mar 4, 2014 · 2 comments
Open

Feature request: support from installing Wordpress from RPM #31

djjudas21 opened this issue Mar 4, 2014 · 2 comments

Comments

@djjudas21
Copy link

At our site we traditionally install Wordpress from an RPM, packaged in the EPEL repo. Would it be possible to allow your module to handle this?

Basically I think it would just need a parameter to tell your module simply to use a package{} resource in Puppet instead of grabbing the tarball from the web and untarring it.

Cheers,
Jonathan

@atxulo
Copy link

atxulo commented Apr 30, 2014

I'd love to see this implemented too.

Until then, as a workaround, you can do this:

  • Create a file wordpress-fake.tar.gz. This file must contain just another file wordpress/index.php, which can be empty if you want.
  • Write a little module than installs Wordpress from an RPM and copies this wordpress-fake.tar.gz to its location before calling wordpress class to install wordpress.

This way, this module doesn't try to download wordpress, then extracts a sigle file from your fake tar.gz, and it will modify /etc/wordpress/wp-config.php and create the database.

  package { 'wordpress' :
    ensure => 'present'.
    before => Class['wordpress'],
  }

file { "/etc/wordpress/wordpress-fake.tar.gz" :
    ensure  => 'present',
    source  => 'puppet:///modules/my_module/wordpress-fake.tar.gz',
}

class { 'wordpress':
    ...

@djjudas21
Copy link
Author

Any progress on this? Thanks 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants