dullyouth / chef-memsql Goto Github PK

The install and default recipes are near-duplicates, and neither one worked exactly right out of the box at the point when I created my fork.

Should I eliminate install and simply leave default? If enough functionality gets added to the installation process to justify multiple recipes for memsqld nodes, I would imagine it would be in either

• things like aggregator/leaf specialization, redundancy, etc., or
• platform_family-specific installation (rpm vs. deb vs. tarball)

and recipes could be spun off along those lines.

Rgds., &c.