Initialize a git repo in the current directory
# git init
Add a remote called "origin"
| # | |
| # Timeout: The number of seconds before receives and sends time out. | |
| # | |
| Timeout 30 | |
| # | |
| # KeepAlive: Whether or not to allow persistent connections (more than | |
| # one request per connection). Set to "Off" to deactivate. | |
| # | |
| KeepAlive On |
Initialize a git repo in the current directory
# git init
Add a remote called "origin"
| "UserData": { | |
| "Fn::Base64": { "Fn::Join":["", [ | |
| "#!/bin/bash -ex\n", | |
| "apt-get update\n", | |
| "apt-get -y install python-setuptools\n", | |
| "mkdir aws-cfn-bootstrap-latest\n", | |
| "curl https://s3.amazonaws.com/cloudformation-examples/aws-cfn-bootstrap-latest.tar.gz | tar xz -C aws-cfn-bootstrap-latest --strip-components 1\n", | |
| "easy_install aws-cfn-bootstrap-latest\n", | |
| "/usr/local/bin/cfn-init --stack ", { "Ref":"AWS::StackName" }, " --resource WebServer", " --region ", { "Ref": "AWS::Region" }, "\n", | |
| "\n", |
| // http://davidwalsh.name/javascript-debounce-function | |
| // Returns a function, that, as long as it continues to be invoked, will not | |
| // be triggered. The function will be called after it stops being called for | |
| // N milliseconds. If `immediate` is passed, trigger the function on the | |
| // leading edge, instead of the trailing. | |
| function debounce(func, wait, immediate) { | |
| var timeout; | |
| return function() { | |
| var context = this, args = arguments; |
| require "spec_helper" | |
| describe ExampleMailer do | |
| describe :new_user do | |
| let(:user) { FactoryGirl.create :user } | |
| it "sends to the correct addresses" do | |
| # :mail is similar to the controller specs 'get', 'post' etc methods | |
| mail :new_user, user |
| ZIP,LAT,LNG | |
| 00601,18.180555, -66.749961 | |
| 00602,18.361945, -67.175597 | |
| 00603,18.455183, -67.119887 | |
| 00606,18.158345, -66.932911 | |
| 00610,18.295366, -67.125135 | |
| 00612,18.402253, -66.711397 | |
| 00616,18.420412, -66.671979 | |
| 00617,18.445147, -66.559696 |
| # db/migrate/XXXXXXXXXXXXX_add_authentication_token_to_users.rb | |
| class AddAuthenticationTokenToUsers < ActiveRecord::Migration | |
| def change | |
| add_column :users, :authentication_token, :string | |
| add_index :users, :authentication_token, :unique => true | |
| end | |
| end |
| Ndabe zitha nkosi yethu mholi wezwe lethu lefatshe la bonata rona lea halalela busa le lizwe bo busa le lizwe bo busa le lizwe bo Lethu busa. Ngoxolo is'khathi sifikile is'khathi busa iyo is'khathi sifikile busa lomhlaba is'khathi sifikile is'khathi sifikile. Busa simba busa bimba. Hem na iyo hem na iyo mem na nkosi bo. Busa simba iyo hem na iyo. Oh busa simba iyo Hem na iyo. Oh busa nkosi bo Hem na nkosi bo. Oh busa simba iyo busa simba iyo. Busa simba iyo ubuse ngo thando. Ubuse ngo thando ubuse. Ngo xolo busa simba, busa simba ubuse ngo xolo. Ubuse ngo thando ubuse ngo xolo. Ubuse ngo thando ubuse ngo xolo. |
RDBMS-based job queues have been criticized recently for being unable to handle heavy loads. And they deserve it, to some extent, because the queries used to safely lock a job have been pretty hairy. SELECT FOR UPDATE followed by an UPDATE works fine at first, but then you add more workers, and each is trying to SELECT FOR UPDATE the same row (and maybe throwing NOWAIT in there, then catching the errors and retrying), and things slow down.
On top of that, they have to actually update the row to mark it as locked, so the rest of your workers are sitting there waiting while one of them propagates its lock to disk (and the disks of however many servers you're replicating to). QueueClassic got some mileage out of the novel idea of randomly picking a row near the front of the queue to lock, but I can't still seem to get more than an an extra few hundred jobs per second out of it under heavy load.
So, many developers have started going straight t