Skip to content

Instantly share code, notes, and snippets.

@Lixivial
Lixivial / confluence_export.sh
Created Mar 3, 2010
shell script to output all Confluence spaces to PDF (and HTML) and place them on a share.
View confluence_export.sh
#!/bin/bash
# set -x
# Jesse Pearson
# Shell script to output all Confluence Spaces to PDF and optionally
# push them to a SMB or some other share.
#
# Dependencies:
# wget
#
# Optional dependencies:
@Lixivial
Lixivial / map_pack.sh
Created Nov 5, 2010
bash script to parse and bundle maps by gametype.
View map_pack.sh
#!/bin/bash
# map_pack.sh - Jesse M. Pearson (Lixivial)
# contact: jesall@gmail.com
#
# Description:
# A simple script meant to break up Nexuiz maps into individual
# gametypes.
#
# Things to note:
# 1. The files generated/used are mostly self-contained to the script's execution directory.
@Lixivial
Lixivial / README
Created Jun 7, 2009
a quick and dirty fallback downloader and load balancer
View README
################
# INSTALLATION #
################
There should be no weird php.ini variables to set, so just move this to a server and set the appropriate permissions.
If you want to make it so a URL can be parsed as http://foo.bar/proxy/param1/param2/paramn, you can utilise a .htaccess
file to do this.
First, rename proxy.php to proxy and then put a .htaccess file in the same directory as proxy with the following information:
<Files proxy>
@Lixivial
Lixivial / backup.pl
Created Apr 5, 2010
a quick perl script to do some backup handling of common data types
View backup.pl
#!/usr/bin/perl
# set -x
# Jesse Pearson
# Quick perl script to tar up given set of targets, and push them to a given destination
#
# Changelog:
# 04.05.2010 - jp - added cp and svn support.
# 04.05.2010 - jp - added local and remote backup holding directories.
# 04.01.2010 - jp - Initial creation date.
#
@Lixivial
Lixivial / infobot.help
Created Nov 17, 2008
Preliminary Infobot qstat wrapper
View infobot.help
qstat: Usage for '## <params>':
qstat: ----- __Aliasing__
qstat: -a - Add an alias
qstat: -c - Check an alias
qstat: -e - Edit an alias
qstat: -r - Remove an alias
qstat: ----- __Querying__
qstat: -h - List of hosts to report/query from.
qstat: -p - Player name to search for in output of -c or -h
qstat: -g - Game type to use to query.
@Lixivial
Lixivial / dbdump_to_sqlite.pl
Created Mar 14, 2010
preliminary vnstat->sqlite converter
View dbdump_to_sqlite.pl
#!/usr/bin/perl
use strict;
use DBI;
use XML::Simple;
use Getopt::Mixed;
# static vars to emulate boolean behaviour.
use constant false => 0;
use constant true => 1;
View gist:3867838

Unhandled guidelines:

  • DG 1-6 (HSTS headers need to be investigated)
  • DG 2-2
  • DG 2-3
  • DG 2-8 (username should be considered sensitive)
  • DG 3-1 (need to expose this in a general sense)
  • DG 3-7 (need to review this in code)
  • DG 3-9 (need to acquire access to their blacklist and then check submitted passwords against it)
  • DG 3-12 (need to confirm this with Jodi)
@Lixivial
Lixivial / email.txt
Last active May 17, 2016
AWS regional and production diagrams
View email.txt
Flow of email through Amazon _________________ ________________________
/ \ / \
___________________________ | regional relay | | postini failover |
/ \ +---> primary.mx. <---+--smtp-+---> outbounds6.obsmtp.com. <-----------------+
| web-1 | | | | | | | |
| primary.apache.web. | | \_________________/ | \________________________/ |
| ________ _______ | | _________________ | ____________________________________ | ___________
| / \ / \ | | / \ | / \ | / \
| | php | | | | | | regional relay | | | Amazon SES fai
View srs-questions.md

Database schema where applicable.

I'd like to discuss this to get a sense of how you guys interpret relationships between data. I'm particularly curious about the following relationships specifically (please forgive me if I'm misusing terms; I'm trying to keep the terms consistent with what I recall you mentioning), but the more schema the merrier here:

  • Realms -> Clients
  • Institutions -> Realms -- particularly in how I seem to recall this being at a yearly level, but I get the sense you have some clients with multiple "cycle runs" a year.
  • Applicants -> Realms
  • Applications -> Realms
  • Applications -> Applicants

Integration needs

This is specifically regarding client's security requirements of data transmission and storage compliance.

@Lixivial
Lixivial / code_deployments
Last active Dec 15, 2015
A standard timeline outlining/explaining code deployments and migrations.
View code_deployments
Code migration and deployment procedures
Outlined below is how code is migrated from branches to trunk with flagged notes outlining where the target
environments actually are.
It also outlines various scenarios, and base term definitions can be found below the diagram.
Diagram
+--------------------------------+