| apply plugin: 'java' | |
| apply plugin : 'war' | |
| group = 'com.cadrlife' | |
| version = '1.0.0' | |
| buildscript { | |
| repositories { | |
| mavenCentral() | |
| } |
| #!/usr/bin/env bash | |
| # Simple move this file into your Rails `script` folder. Also make sure you `chmod +x puma.sh`. | |
| # Please modify the CONSTANT variables to fit your configurations. | |
| # The script will start with config set by $PUMA_CONFIG_FILE by default | |
| PUMA_CONFIG_FILE=config/puma.rb | |
| PUMA_PID_FILE=tmp/pids/puma.pid | |
| PUMA_SOCKET=tmp/sockets/puma.sock |
| #!/usr/bin/env python | |
| # -*- coding: utf-8 -*- | |
| def archive_to_bytes(archive): | |
| def to_seconds(s): | |
| SECONDS_IN_A = { | |
| 's': 1, | |
| 'm': 1 * 60, | |
| 'h': 1 * 60 * 60, |
| #!/usr/bin/env ruby | |
| #------------------------------------------------------------------------------ | |
| # Aggregate Print useful information from /proc/[pid]/smaps | |
| # | |
| # pss - Roughly the amount of memory that is "really" being used by the pid | |
| # swap - Amount of swap this process is currently using | |
| # | |
| # Reference: | |
| # http://www.mjmwired.net/kernel/Documentation/filesystems/proc.txt#361 |
| # _utils.sh --- Utilities used across all the scripts. | |
| set -e | |
| set -o pipefail | |
| # Prints spaces as a prefix to the command's output. | |
| function prefixed { | |
| sed -e "s/^/ /" | |
| } |
Eric Bidelman has documented some of the common workflows possible with headless Chrome over in https://developers.google.com/web/updates/2017/04/headless-chrome.
If you're looking at this in 2016 and beyond, I strongly recommend investigating real headless Chrome: https://chromium.googlesource.com/chromium/src/+/lkgr/headless/README.md
Windows and Mac users might find using Justin Ribeiro's Docker setup useful here while full support for these platforms is being worked out.
AWS OpsWorks, formerly Scalarium, is a chef-based system that deeply integrates with EC2 (security policies, key pairs, etc). OpsWorks acts as web console to configure your entire system, and as a command hub for running chef-solo on all the instances.
A stack represents a collection of inter-connected and inter-configured services.
A stack has lifecycle events which are triggered by any change to the stack configuration (such as, adding a new instance to a layer, or changing the hosts of an application). In this way, the stack acts as an event hub, notifying every instance of any changes.
| max_connections = 1500 # (change requires restart) | |
| shared_buffers = 12000MB # min 128kB, based on 80GB RAM DB | |
| temp_buffers = 8MB # min 800kB | |
| work_mem = 64MB # min 64kB | |
| maintenance_work_mem = 1500MB # min 1MB | |
| wal_level = hot_standby # minimal, archive, or hot_standby | |
| checkpoint_segments = 256 # in logfile segments, min 1, 16MB each | |
| checkpoint_completion_target = 0.9 # checkpoint target duration, 0.0 - 1.0 | |
| max_wal_senders = 6 # max number of walsender processes |
| #! /usr/bin/env python | |
| from boto.ses.connection import SESConnection | |
| import os | |
| import sys | |
| import subprocess | |
| import socket | |
| TMPFILE = '/var/run/postgresql/last-wal-archive-error-file.tmp' | |
| if __name__ == '__main__': |
