| <?php if ( ! defined('BASEPATH')) exit('No direct script access allowed'); | |
| class MY_Session extends CI_Session{ | |
| private $sess_use_redis = TRUE; | |
| private $redis = ''; | |
| public function __construct($params = array()) { | |
| //parent::__construct(); | |
| $this->CI =& get_instance(); |
| Capistrano::Configuration.instance(:must_exist).load do | |
| # example execution 'cap bundle_app -s version=HEAD' | |
| desc "Bundle code and push to S3" | |
| task :bundle_app do | |
| puts "Starting Git archive of #{version}" | |
| `git archive -o oldweather.tar #{version}` | |
| `gzip oldweather.tar` | |
| s3_upload | |
| clean_up |
| #!/home/ec2-user/.rvm/rubies/ruby-1.9.2-p0/bin/ruby | |
| require 'rubygems' | |
| require 'aws/s3' | |
| require 'fileutils' | |
| AWS::S3::Base.establish_connection!( | |
| :access_key_id => 'access_key', | |
| :secret_access_key => 'secret_key' | |
| ) |
This is a simple way to backup your MySQL tables to Amazon S3 for a nightly backup - this is all to be done on your server :-)
Sister Document - Restore MySQL from Amazon S3 - read that next
this is for Centos 5.6, see http://s3tools.org/repositories for other systems like ubuntu etc
This is a hands-on way to pull down a set of MySQL dumps from Amazon S3 and restore your database with it
Sister Document - Backup MySQL to Amazon S3 - read that first
# Set our variables
export mysqlpass="ROOTPASSWORD"
| DELIMITER $$ | |
| DROP PROCEDURE IF EXISTS `CopyDB` $$ | |
| CREATE PROCEDURE `CopyDB` (sourceDB VARCHAR(64),targetDB VARCHAR(64)) | |
| TheStoredProcedure:BEGIN | |
| DECLARE found_count,ndx,ndx_last INT; | |
| DECLARE sqlcmd VARCHAR(1024); | |
| SELECT COUNT(1) INTO found_count | |
| FROM information_schema.tables |
| // jshint node:true | |
| 'use strict'; | |
| var semver = require('semver'), | |
| exec = require('exec'); | |
| module.exports = function(grunt) { | |
| 'use strict'; | |
| require('load-grunt-tasks')(grunt); |
| // Copyright 2014 A Medium Corporation | |
| // | |
| // z-index.less | |
| // Medium.com's z-index scale. Z-index values should always be defined in z-index.less. This | |
| // allows us to at a glance determine relative layers of our application and prevents bugs | |
| // arrising from arbitrary z-index values. Do not edit the z-index scale! Only add application | |
| // scoped z-index values. | |
| // Z-Index Scale (private vars) |
Subject: Apologies for the downtime, but we're coming back stronger.
Dear Simon,
As you may already know, BrowserStack experienced an attack on 9th November, 2014 at 23:30 GMT during which an individual was able to gain unauthorized access to some of our users’ registered email addresses. He then tried to send an email to all our registered users, but he was only able to reach less than 1% (our estimate is 5,000 users). The email contained inaccurate information, even claiming that BrowserStack would be shutting down.
When we realized this, our only concern was to protect our users. This involved temporarily taking down the service, as we scrutinized each component carefully. This inconvenienced our users for several hours, and for that we are truly sorry.
What happened?