Spencer Owen spuder

Tried installing dashing again on mac using ruby 1.9 as suggested by David Onagro

gem uninstall dashing
gem uninstall thin
gem clean

sles-packages:~ # kiwi -p /usr/share/doc/packages/kiwi/examples/suse-13.1/suse-docker-container \
>      --root /tmp/mycontainer
Jul-07 20:14:37 <1> : Description provides no MD5 hash, check
Jul-07 20:14:37 <1> : Reading image description [Prepare]...
Jul-07 20:14:37 <1> : Setting up package manager: zypper                                                                                                                  done
Jul-07 20:14:37 <1> : Setting up source channel:
Jul-07 20:14:37 <1> : --> opensuse://13.1/repo/oss/
Jul-07 20:14:38 <1> : Set root log: /tmp/mycontainer.21413.screenrc.log...                                                                                                done
Jul-07 20:14:38 <1> : Creating default template files for new root system                                                                                                 done

Can't get dashing working, here is what I have done.

gem install dashing
dashing new foobar
bundle
dashing generate dashboard foo
dashing start

How do you created defined types in the foreman? e.g. nrpe::command, apahce::vhost ect.. Based on these links, and from what users in the foreman irc chanel have suggested. https://github.com/theforeman/foreman-infra/blob/master/puppet/modules/users/manifests/init.pp https://groups.google.com/forum/#!topic/foreman-users/o-Sqjo-n21A

profile::nagios::client.pp

class profiles::nagios::client ( $checks ){
include nrpe
 if $checks {

	# -- mode: ruby --
	# vi: set ft=ruby :

	# Vagrantfile API/syntax version. Don't touch unless you know what you're doing!
	VAGRANTFILE_API_VERSION = "2"

	Vagrant.configure(VAGRANTFILE_API_VERSION) do \|config\|

	config.vm.synced_folder "../", "/vagrant_data" # Mount directory up a level so puppet module list can find modules
	config.vm.synced_folder ".", "/vagrant"

	#!/usr/bin/env bash
	# A simple script to build a docker container
	# Pre and Post functions are where you place any optional commands (eg. git clone)

	# Sets name for docker container docker build -t 'foo/bar:latest
	readonly DOCKER_USER='foo'
	readonly DOCKER_NAME='bar'
	readonly DOCKER_TAG='latest'

	# Mac and boot2docker don't use root for docker command

	# Functions to clean up docker containers on mac
	# Based on this blog article, however is more mac friendly (no xargs -r)
	# http://blog.stefanxo.com/2014/02/clean-up-after-docker/

	# Searches for images and containers that are named/tagged with '<none>' and removes them
	# If no results, prints out the usage information


	#Create functions since aliases don't play nicely with subshells
	dci() {

	How the heck are you supposed to edit the description?

	See how I take the readme.md from here and add it to my metadata.json
	https://github.com/spuder/puppet-gitlab/blob/master/README.md

	You have to scroll hundreds of lines right!

	https://tickets.puppetlabs.com/browse/GEP-9?jql=project%20%3D%20GEP%20AND%20text%20~%20%22metadata.json%22

	{

	[root@gitlab tmp]# gitlab-ctl reconfigure
	Starting Chef Client, version 11.12.2
	Compiling Cookbooks...
	Recipe: gitlab::default
	* directory[/etc/gitlab] action create (up to date)
	[2014-10-01T16:41:46-06:00] WARN: Cloning resource attributes for directory[/var/opt/gitlab] from prior resource (CHEF-3694)
	[2014-10-01T16:41:46-06:00] WARN: Previous directory[/var/opt/gitlab]: /opt/gitlab/embedded/cookbooks/gitlab/recipes/default.rb:40:in `from_file'
	[2014-10-01T16:41:46-06:00] WARN: Current directory[/var/opt/gitlab]: /opt/gitlab/embedded/cookbooks/gitlab/recipes/users.rb:23:in `from_file'
	[2014-10-01T16:41:46-06:00] WARN: Cloning resource attributes for directory[/var/opt/gitlab/gitlab-rails/etc] from prior resource (CHEF-3694)
	[2014-10-01T16:41:46-06:00] WARN: Previous directory[/var/opt/gitlab/gitlab-rails/etc]: /opt/gitlab/embedded/cookbooks/gitlab/recipes/gitlab-rails.rb:37:in `block in from_file'

	# The client must have an x11 window running (for the graphics)

	ssh foo@192.0.2.0 tail -f /home/foo/logstalgia.log \| logstalgia --sync

	Verify that the logstalgia-client can ssh to the logstalgia-server without passwords by setting up ssh key access