whyvez

README is empty

whyvez

for memo in *.memo
do 
  awk 'NR == 1 {gsub("*", ""); gsub("/", ""); filename = $0 "-" FILENAME} NR > 1 {print $0 >> "new/" filename}' $memo
done

whyvez

/* 
 The current container reuse strategy in AWS Lambda makes it very hard to ensure consistent environments between invocations. 
 Managing environments is currently the responsibility of the user. There should be some additional cleanup tasks ran after 
 an invocation to ensure at least a freah new nodejs context. As an example I added the setInterval issue we've seen.
*/

// new container a
// * invocation 1 on container a
//   - using setInterval to check remaining time every 1 sec

whyvez

#!/usr/bin/env bash

wget http://invisible-island.net/datafiles/release/mawk.tar.gz
tar -xzvf mawk.tar.gz
cd mawk-1.3.4-20150503
./configure
make
sudo make install

whyvez

http://www.postgresql.org/docs/9.1/static/app-vacuumdb.html

https://wiki.postgresql.org/wiki/Disk_Usage

whyvez

#!/bin/bash
SERVER=yourwebsite.com
tar -cjf- ~/.crypt/passwd ~/.ssh ~/.bashrc ~/.profile ~/.vimrc ~/.gitconfig \
~/.config/chromium ~/.mozilla \
  | openssl enc -aes-256-cbc \
  | ssh $SERVER 'cat>~/www/backup/`date +%F.%T`'
ssh $SERVER 'ls -1 ~/www/backup | grep ^[0-9] | sort > ~/www/backup/list.txt'

whyvez

url.parse('s3://tesera.datathemes/tesera.afgo.pgyi/uploads/yves.richard@tesera.com/aply/e11cb037-1b1d-432a-ab33-c41025b41cde/stage/datapackage.zip')

{
  "protocol": "s3:",
  "slashes": true,
  "auth": null,
  "host": "tesera.datathemes",
  "port": null,
  "hostname": "tesera.datathemes",

whyvez

sudo su -

whyvez

COMPANY=TSI; mkdir -p $COMPANY; for csv in *.csv; do awk -F,  -v COMPANY=$COMPANY 'NR > 1 {OFS=","; $1=COMPANY}1' $csv > ./$COMPANY/$csv; done

whyvez

#!/usr/bin/env bash

# checks pgyi dataset for fkey integrity
# will print out any offending records
# usage: bash ./fkeycheck.sh <csv_data_folder>
# example: bash ./fkeycheck.sh ./examples/pgyi/data

wd=$1

plot=$wd/plot.csv