Split install resource into install / configure in next major revision? about redisio HOT 7 CLOSED

It's clear that the installation should NOT be done in the provider but instead in the recipe itself. This would simply the resource for configuring redis. This could be a breaking change so i will bump the cookbooks minor version for this even though it will not add any significant feature, other than making the cookbook more sensible and easy to maintain / undersand.

from redisio.

As far as I can tell there is no way to currently install with the package LWRP and it only installs from source. It seems like this change would support package based install. Having a package based install would mean we could contribute to this cookbook rather than maintaining our own.

from redisio.

That's pretty much the intent of this ticket. The idea is for the next big revision of the cookbook to decouple the installing of the binaries and the configuration. This will make it much easier and cleaner to alter HOW the package is installed. It should probably also use ARK to download and install the tarball.

from redisio.

Now that we have install separated, does contributing an redisio::install_package recipe make sense? I'd love to see this added and prefer some guidance on how to approach. Maybe we can make it part of 2.0

from redisio.

I think it makes sense to allow for installation of redis from more than just source. This could introduce some fun complications due to where those packages might expect configuration files. I can't imagine it will be THAT bad though.

I do intend to also rework the way in which the cookbook generates configuration files as well though. It need to generate them pragmatically, not the silly hardcoded way it does now that requires actually updating the recipe every time a new configuration option comes out.

On Jun 27, 2013, at 17:01, Sander van Zoest [email protected] wrote:

Now that we have install separated, does contributing an redisio::install_package recipe make sense? I'd love to see this added and prefer some guidance on how to approach. Maybe we can make it part of 2.0

—
Reply to this email directly or view it on GitHub.

from redisio.

Closing this issue as it is working and implemented in the 2.0.0_wip branch. I will create a separate issue for allowing installation of redis from package instead of source.

from redisio.

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

from redisio.