Sean O'Donnell sodonnell

## Add basic php-fpm proxy to apache config
echo -e "<FilesMatch \\.php$>\n\tSetHandler \"proxy:fcgi://127.0.0.1:9000\"\n</FilesMatch>\n\n" >> /etc/httpd/conf/httpd.conf;

## install.awscli.sh
yum -y install python34 python34-pip
pip3 install --upgrade pip
pip3 install awscli

## test.pquery.pl
#!/usr/bin/perl
use strict;
use warnings;

# install pQuery:
# sudo cpanm pQuery;
use pQuery;

my $url = "https://github.com/sodonnell/plowbot/";

## f.u.amazon.rds.super.privs.sh
sed -i 's/\/\*[^*]*DEFINER=[^*]*\*\///' dump2rds.sql

## postsuper
mailq
postsuper -d $(mail_queue_id)

## myisam2innodb.sh
#!/usr/bin/env bash
#
# This was commented on the following page:
# https://dev.mysql.com/doc/refman/8.0/en/converting-tables-to-innodb.html
#
# This script/command was tested and found to be harmless/non-destructive, surprisingly. ;-P
#
DBNAME="exampledb";
DBHOST="localhost";
DBUSER="someguy";

## aws.rds.restore.snapshot.sh
#!/usr/bin/env bash
#
# Restore/Re-Deploy an Amazon RDS (MySQL) Database Instance from a specified snapshot.
#
# This script is intended to be run on an AWS EC2 instance
# within an isolated VPC infrastructure, to restore or re-deploy a
# test/staging database instance from a the latest
# 'production database' snapshot.
#
# This script requires the latest aws-cli program.

## nmap.sh
#!/usr/bin/env bash
#
# Run various nmap scans on a hostname and log all scans to a single file.
#
# Alternatively, nmap does support log-output arguments on it's own, but the problem is
# grouping various scans that often conflict during the same process, thus requiring
# a series of multiple scans and would create multiple logs.
#
# usage examples:
# default scan:

## ntpdate.sh
#!/usr/bin/env bash
# install ntp service and sync w/ the pool
# why wasn't this done on these old servers. smh
yum -y install ntp;
chkconfig ntpd on;
service ntpd start;
date -R; ntpq -p; date -R;
ntpdate -q  0.ro.pool.ntp.org  1.ro.pool.ntp.org

## rds.hosts.sync.sh
#!/usr/bin/env bash
#
# This script is a complete hack to work-around a crappy
# old Amazon EC2 instance running a custom CentOS AMI that
# was NOT provisioned by Amazon AWS engineers.
#
# This particular (bain of my existence) server uses
# Google's DNS servers in the /etc/resolv.conf file, but
# wreaks havoc on the PHP web application when trying to
# call mysqli_connect, and often times-out or takes far
	yum -y install python34 python34-pip
	pip3 install --upgrade pip
	pip3 install awscli
	#!/usr/bin/perl
	use strict;
	use warnings;

	# install pQuery:
	# sudo cpanm pQuery;
	use pQuery;

	my $url = "https://github.com/sodonnell/plowbot/";
	#!/usr/bin/env bash
	#
	# This was commented on the following page:
	# https://dev.mysql.com/doc/refman/8.0/en/converting-tables-to-innodb.html
	#
	# This script/command was tested and found to be harmless/non-destructive, surprisingly. ;-P
	#
	DBNAME="exampledb";
	DBHOST="localhost";
	DBUSER="someguy";
	#!/usr/bin/env bash
	#
	# Restore/Re-Deploy an Amazon RDS (MySQL) Database Instance from a specified snapshot.
	#
	# This script is intended to be run on an AWS EC2 instance
	# within an isolated VPC infrastructure, to restore or re-deploy a
	# test/staging database instance from a the latest
	# 'production database' snapshot.
	#
	# This script requires the latest aws-cli program.
	#!/usr/bin/env bash
	#
	# Run various nmap scans on a hostname and log all scans to a single file.
	#
	# Alternatively, nmap does support log-output arguments on it's own, but the problem is
	# grouping various scans that often conflict during the same process, thus requiring
	# a series of multiple scans and would create multiple logs.
	#
	# usage examples:
	# default scan:
	#!/usr/bin/env bash
	# install ntp service and sync w/ the pool
	# why wasn't this done on these old servers. smh
	yum -y install ntp;
	chkconfig ntpd on;
	service ntpd start;
	date -R; ntpq -p; date -R;
	ntpdate -q 0.ro.pool.ntp.org 1.ro.pool.ntp.org
	#!/usr/bin/env bash
	#
	# This script is a complete hack to work-around a crappy
	# old Amazon EC2 instance running a custom CentOS AMI that
	# was NOT provisioned by Amazon AWS engineers.
	#
	# This particular (bain of my existence) server uses
	# Google's DNS servers in the /etc/resolv.conf file, but
	# wreaks havoc on the PHP web application when trying to
	# call mysqli_connect, and often times-out or takes far