Forge Home


Manage MySQL Server on Mac OS X.


12,452 latest version

3.3 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 0.0.2 (latest)
  • 0.0.1
released Aug 28th 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.



bjoernalbers/mysql_osx — version 0.0.2 Aug 28th 2012


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