Instantly share code, notes, and snippets.

View gist:33e994563addbff62d3c3807c6e8bf55
vagrant@jessie:~/buildroot$ make
[COWBUILDER] _build/RPMS/ocaml-findlib_1.5.5-1_amd64.deb
-> Copying COW directory
forking: rm -rf /var/cache/pbuilder/build//cow.3327
forking: cp -al /var/cache/pbuilder/base.cow /var/cache/pbuilder/build//cow.3327
I: removed stale ilistfile /var/cache/pbuilder/build//cow.3327/.ilist
forking: chroot /var/cache/pbuilder/build//cow.3327 cowdancer-ilistcreate /.ilist find . -xdev -path ./home -prune -o \( \( -type l -o -type f \) -a -links +1 -print0 \) | xargs -0 stat --format '%d %i '
-> Invoking pbuilder
forking: pbuilder build --configfile pbuilder/pbuilderrc --buildplace /var/cache/pbuilder/build//cow.3327 --buildresult RPMS --debbuildopts --no-targz --internal-chrootexec chroot /var/cache/pbuilder/build//cow.3327 cow-shell /home/vagrant/buildroot/SRPMS/ocaml-findlib_1.5.5-1.dsc
W: /root/.pbuilderrc does not exist
View gist:d9d17707528f76659fe716c6337ab3f4
filebeat:
output:
elasticsearch:
hosts: ["127.0.0.1:9200"]
logstash:
hosts: ["127.0.0.1:5044"]
prospectors:
-
input_type: log
paths:
View output.txt
filebeat:
config:
filebeat:
# List of prospectors to fetch data.
prospectors:
# Each - is a prospector.
-
paths:
- "/var/log/daemon.log"
View Makefile.am
AUTOMAKE_OPTIONS := subdir-objects
ACLOCAL_AMFLAGS := -I m4
bin_PROGRAMS = src/statsite
noinst_LTLIBRARIES = deps/ae/ae.a deps/inih/ini.a deps/murmurhash/MurmurHash3.a
noinst_HEADER = $(lib_ae_includes) $(lib_inih_includes) $(lib_murur_includes)
View gist:530a6a2a2e68b1116d0b
file_roots:
base:
- /srv/salt/state/env/base
- /srv/salt/state/formulas
prod:
- /srv/salt/state/env/prod
- /srv/salt/state/env/base
- /srv/salt/state/formulas
act:
- /srv/salt/state/env/act
View Server.app.txt
This file has been truncated, but you can view the full file.
.
./_CodeSignature
./_CodeSignature/CodeResources
./_MASReceipt
./_MASReceipt/receipt
./Frameworks
./Frameworks/Server.framework
./Frameworks/Server.framework/Resources
./Frameworks/Server.framework/Server
View gist:4b4411074a5f0300374a
{%- if 'userlists' in salt['pillar.get']('haproxy', {}) %}
{%- for id, userlist in salt['pillar.get']('haproxy:userlists').iteritems() %}
userlist {{ id }}
{%- for entry in userlist.iteritems() %}
{{ entry }}
{%- endfor %}
{% endfor %}
{% endif %}
View Client-node-PufferPanel-setup.md
  1. Install the node itself

    Installing the node requires you to setup a few files, a web interface, a SSH user, sudo access for that user, pubkey authentication and a shared AES key.

    So, let's start by getting the required files:

    git clone https://github.com/DaneEveritt/PufferPanel.git

    [ COPY FILES TO PLACES AND SUCH ]

View gist:9423232

Setting up PufferPanel installation on Debian Wheezy (Debian Stable 2013-2014) 7.4

What you basically need to do:

A. Setup at least 1 master node B. Setup at least 1 client node

This requires vhosts and certain tools and dependencies. Each node setup list allows you to perform all tasks for setting this up for the node type. First, you'll set up the node environments and the master, next you set up the node communication, storage locations and client nodes.

View PufferPanel Setup Debian
Setting up PufferPanel master on Debian Wheezy (Debian Stable 2013-2014)
What you basically need to do:
1. Clone from https://github.com/DaneEveritt/PufferPanel.git for each node type
2. Setup at least 1 master node
3. Setup at least 1 client node
This requires vhosts and certain tools and dependencies. Each node setup list allows you to perform all tasks for setting this up for the node type.
First, you'll set up the node environments and the master, next you set up the node communication, storage locations and client nodes.