type below:
brew update
brew install redis
To have launchd start redis now and restart at login:
brew services start redis
| Install Ruby Gems on Mac OS X without sudo | |
| 1. Add GEM_HOME to your .bash_profile | |
| For example, nano ~/.bash_profile and add | |
| export GEM_HOME=/Users/srinivas/.gem where the path is to your own Home folder | |
| 2. Add the gem executables to your system path | |
| Also in .bash_profile, add | |
| import android.util.Log; | |
| import java.io.IOException; | |
| import java.net.InetAddress; | |
| import java.net.Socket; | |
| import java.net.SocketException; | |
| import java.net.UnknownHostException; | |
| import javax.net.SocketFactory; |
| # Borrowed from: | |
| # https://github.com/silven/go-example/blob/master/Makefile | |
| # https://vic.demuzere.be/articles/golang-makefile-crosscompile/ | |
| BINARY = superdo | |
| VET_REPORT = vet.report | |
| TEST_REPORT = tests.xml | |
| GOARCH = amd64 | |
| VERSION?=? |
type below:
brew update
brew install redis
To have launchd start redis now and restart at login:
brew services start redis
| #!/bin/bash | |
| # based on https://lebkowski.name/docker-volumes/ | |
| # remove exited containers: | |
| docker ps --filter status=dead --filter status=exited -aq | xargs -r docker rm -v | |
| docker volume ls -qf dangling=true | xargs -r docker volume rm | |
| # remove unused images: | |
| docker images --no-trunc | grep '<none>' | awk '{ print $3 }' | xargs -r docker rmi |
| #!/bin/bash | |
| ################################################################################ | |
| # Rather than run postgres in its own container, we want to run it on | |
| # the (Ubuntu) host and allow: | |
| # | |
| # + peer connections on the host | |
| # + local md5 connections from any docker container | |
| # | |
| # THIS IS COPY/PASTED FROM COMMAND LINE INPUT AND IS UNTESTED AS A SINGLE SCRIPT | |
| ################################################################################ |
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
| DRONE_HOST=https://loc-drone-ci.localtunnel.me | |
| DRONE_GITHUB_CLIENT=af516d1889d283a6a30d | |
| DRONE_GITHUB_SECRET=64994dabf745bc5076734aeff4cb41cd268782f8 | |
| DRONE_SECRET=drone-local-bla-bla-bla |