The module is not maintained anymore and archived.

B2DROP deployment recipes for puppet

Table of Contents

1. Module Description - What the module does and why it is useful
2. Setup - The basics of getting started with b2drop
   • What puppet-b2drop affects
   • Beginning with b2drop
3. Usage - Configuration options and additional functionality
4. Limitations - OS compatibility, etc.
5. Development - Guide for contributing to the module
6. Testing - Instructions to test the code

Module Description

This module adds the repositories for b2drop to the apps and themes folder. It also configures webserver and database.

Setup

On your puppet master, go to the environment that the actual b2drop server belongs to. Inside of the module directory of that environment simply clone this repository

git clone https://github.com/EUDAT-B2DROP/b2drop-puppet.git b2drop 

What puppet-b2drop affects

• apache, mysql, php7, cron, tmp, logrotate

Beginning with b2drop

The following snippet will enable a all in one machine (LAMP stack + nextcloud + b2drop) on one server.

    class { 'b2drop': }

Usage

The b2drop class configures apache, mysql and the repositories for the b2drop extensions.

To deploy B2DROP on a host, just add

include ::b2drop

to the node and add missing variables for b2drop::apache and b2drop::mysql using hiera.

Limitations

We are focussing on CentOS, other operating systems should work as well due to apache/mysql/vcsrepo. You may disable selinux then.

Development

There are no formal requirements to participate. If there are questions, feel free to contact the authors mentioned in AUTHORS.md

Testing

For testing the code with puppet utils, make sure you have ruby and bundler installed and then execute:

mkdir vendor
export PUPPET_GEM_VERSION="~> 4.8.0"
export GEM_HOME=vendor
bundle install
bundle exec rake test