Skip to content

Instantly share code, notes, and snippets.

View slyness's full-sized avatar
🏠
Working from home

Aaron Baer slyness

🏠
Working from home
14 followers · 13 following
View GitHub Profile
@slyness
slyness / client.sh
Created April 30, 2014 17:06 — forked from nstielau/client.sh
echo '{
"handlers": ["debug"],
"name": "push_woot_test",
"output": "woot!",
"status": 0
}' | nc -w1 127.0.0.1 3030
@slyness
slyness / CONTRIBUTING.md
Last active August 29, 2015 14:00 — forked from dje/CONTRIBUTING.md
  1. Fork the repository using Github
  2. Checkout a named feature branch created from the develop branch
  3. Complete modifications or corrections, include tests to support your code
  4. Run the tests, ensuring they all pass
  5. Submit a Pull Request to the develop branch using Github
@slyness
slyness / client.sh
Created April 18, 2014 23:09 — forked from nstielau/client.sh
echo '{
"handlers": ["debug"],
"name": "push_woot_test",
"output": "woot!",
"status": 0
}' | nc -w1 127.0.0.1 3030
@slyness
slyness / upgrade.md
Created March 28, 2014 03:44 — forked from jeremiahsnapp/upgrade.md

All upgrades

All upgrades should be performed first with a copy of Production data, in an environment that is non-essential. This could be a Vagrant VM and is our typical test hardware for this purpose.

Backups are good to have for many reasons at all times. Especially during upgrades, tested backups become a critical part of our toolkit.

Upgrading from OPC1.2.x

Upgrading from OPC1.2x to EC11x REQUIRES that you first upgrade all systems in a cluster to OPC1.4.6.