| # This is an example of the Stack Exchange Tier 1 HAProxy config | |
| # The only things that have been changed from what we are running are: | |
| # 1. User names have been removed | |
| # 2. All Passwords have been remove | |
| # 3. IPs have been changed to use the example/documentation ranges | |
| # 4. Rate limit numbers have been changed to randome numbers, don't read into them | |
| userlist stats-auth | |
| group admin users $admin_user | |
| user $admin_user insecure-password $some_password |
| Solarized | |
| #FDF6E3,#EEE8D5,#93A1A1,#FDF6E3,#EEE8D5,#657B83,#2AA198,#DC322F | |
| Solarized Dark | |
| #073642,#002B36,#B58900,#FDF6E3,#CB4B16,#FDF6E3,#2AA198,#DC322F | |
| # ----------------------------------------------- | |
| # ENSURE GIT REPOSITORIES | |
| - name: Git | Ensure server repository | |
| sudo_user: git | |
| git: repo={{ upstream }} | |
| dest={{ repo_dir }} | |
| bare=yes | |
| update=no | |
| tags: git |
| # -*- mode: ruby -*- | |
| # vi: set ft=ruby : | |
| # This configuration requires Vagrant 1.5 or newer and two plugins: | |
| # | |
| # vagrant plugin install vagrant-hosts ~> 2.1.4 | |
| # vagrant plugin install vagrant-auto_network ~> 1.0.0 | |
| # | |
| # After installation, the following steps will spin up a master and agent that | |
| # can communicate with each other: |
#A script to post back to Slack via the webhooks API
##why this exists?
Slack's own hubot adapter needs the hubot installation to be accessible via web. This can be problematic in some cases, as a security risk.
This hack let's you run your Hubot behind a firewall, and connect to Slack via the IRC gateway.
To respond, Hubot uses the incoming webhooks end-point of Slack.
| if exists("g:loaded_syntastic_clint_checker") | |
| finish | |
| endif | |
| let g:loaded_syntastic_clint_checker = 1 | |
| let s:save_cpo = &cpo | |
| set cpo&vim | |
| function! SyntaxCheckers_c_clint_GetLocList() dict | |
| let makeprg = self.makeprgBuild({ |
| wget http://stedolan.github.io/jq/download/linux64/jq | |
| aws ec2 describe-instances --filters "Name=tag:Name,Values=$NAME" \ | |
| "Name=instance-state-name,Values=running" \ | |
| | jq -r \ | |
| ".Reservations[] | .Instances[] | .InstanceId" \ | |
| aws ec2 describe-volumes --filters \ | |
| "Name=status,Values=available" \ | |
| | jq -r ".Volumes[] | .VolumeId" \ |
| # to generate your dhparam.pem file, run in the terminal | |
| openssl dhparam -out /etc/nginx/ssl/dhparam.pem 2048 |
So, you made a change to your dashboard, and now you have to run all over the building, plugging in a keyboard, and reloading the dashboard on the various TVs in your office. What if you could reload all the dashboard from the comfort of your desk?
Add this widget to the very bottom of your dashboard, after the "gridster" div:
<div class="gridster">
<ul>
<li data-row="1" data-col="1" data-sizex="1" data-sizey="1">
<div data-view="Image" data-image="/benbria/loop.png" style="background-color:#666766"></div>
</li>
The graphing widget shows graphs using the Rickshaw graphing library. The names of data fields should be (vaguely) familiar if you've used Rickshaw before.
It's recommended that you replace the /assets/javascripts/rickshaw.min.js from your dashboard with the latest from here.