ror, scala, jetty, erlang, thrift, mongrel, comet server, my-sql, memchached, varnish, kestrel(mq), starling, gizzard, cassandra, hadoop, vertica, munin, nagios, awstats
# Modify this file accordingly for your specific requirement. | |
# http://www.thegeekstuff.com | |
# 1. Delete all existing rules | |
iptables -F | |
# 2. Set default chain policies | |
iptables -P INPUT DROP | |
iptables -P FORWARD DROP | |
iptables -P OUTPUT DROP |
# +----------------------------+ | |
# | IDE files | | |
# +----------------------------+ | |
/.idea | |
# +----------------------------+ | |
# | Vagrant | | |
# +----------------------------+ | |
/.vagrant |
This work is licensed under CC BY-NC-SA 4.0. See Editorial Notes for Attribution details.
DISCLAIMER: This research and investigation work is based on several years of experience within the Matrix ecosystem and validation of facts via public and private communication. Reverse engineering was used to ensure some of the statements presented as facts regarding implementations are accurate. >
# Usage | |
# host supply IP | |
# -t(tags) run specific tasks ie. db=master, dbslave=slave1/2, promote=update slave to master, remove= remove host | |
# ansible-playbook pg.yml -e "host=192.169.99.2 -t db ##Build Master | |
# ansible-playbook pg.yml -e "host=192.168.99.3" -t dbslave ##Build Slave | |
# ansible-playbook pg.yml -e "host=192.168.99.3" -t promote ##Promoe slave to master | |
# ansible-playbook pg.yml -e "host=192.168.99.2" -t remove ##Remove node from cluster | |
# ansible-playbook /var/lib/pgsql/pg.yml -e "host=192.168.99.4" -s -t db --user=user1 --ask-sudo-pass ##Ubuntu | |
# Created Bimal Patel | |
--- |
#!/usr/bin/env bash | |
# https://code.google.com/p/chromium/issues/detail?id=226801 | |
url='https://chromium.googlesource.com/chromium/src/net/+/master/http/transport_security_state_static.json?format=TEXT'; | |
curl -#s "${url}" | \ | |
base64 --decode | \ | |
sed '/^ *\/\// d' | \ | |
sed '/^\s*$/d' > hsts.json; |
This document is research for the selection of a communication platform for robot-net.
The purpose of this component is to enable rapid, reliable, and elegant communication between the various nodes of the network, including controllers, sensors, and actuators (robot drivers). It will act as the core of robot-net to create a standardized infrastructure for robot control.
Requirements: