mysql_osx

contributions requested
Manage MySQL Server on Mac OS X.

12,928 downloads

12,567 latest version

3.3 quality score

Support the Puppet Community by contributing to this module

You are welcome to contribute to this module by suggesting new features, currency updates, or fixes. Every contribution is valuable to help ensure that the module remains compatible with the latest Puppet versions and continues to meet community needs. Complete the following steps:

  1. Review the module’s contribution guidelines and any licenses. Ensure that your planned contribution aligns with the author’s standards and any legal requirements.
  2. Fork the repository on GitHub, make changes on a branch of your fork, and submit a pull request. The pull request must clearly document your proposed change.

For questions about updating the module, contact the module’s author.

Version information

  • 0.0.2 (latest)
  • 0.0.1
released Aug 29th 2012

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'bjoernalbers-mysql_osx', '0.0.2'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add bjoernalbers-mysql_osx
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install bjoernalbers-mysql_osx --version 0.0.2

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.

Download

Documentation

bjoernalbers/mysql_osx — version 0.0.2 Aug 29th 2012

$Id$

To run all tests, run: 'rake test'. To run an individual suite, run the file directly. e.g. cd test/util; ./utiltest.rb

You might need to run some tests as root.

If you do not have rake installed: gem install rake

The following information is possibly out of date?

Tests are organized into a dual hierarchy: each subdirectory is considered a test suite, and each file in the subdirectory is considered a test case. You can use any test case as an example of how to write more of them, but basically the only requirements are that they each have their own class names, their names each match /tc_.+.r/, and that they have the following header:

if FILE == $0 $:.unshift '..' $:.unshift '../../lib' $blinkbase = "../.." end