Hi there!
The docker cheat sheet has moved to a Github project under https://github.com/wsargent/docker-cheat-sheet.
Please click on the link above to go to the cheat sheet.
#!/usr/bin/env bash | |
set -o errexit | |
set -o xtrace | |
# Provide the "language" as $TRAVIS_LANGUAGE or first positional argument. Available languages | |
# at the time of this writing are: | |
# | |
# android | |
# erlang |
language: objective-c | |
xcode_workspace: "<WorkspaceName.xcworkspace>" | |
xcode_scheme: "<SchemaName>" | |
script: xctool -workspace <WorkspaceName.xcworkspace> -scheme <SchemeName> -configuration Release build archive | |
before_script: | |
- ./scripts/travis/add-key.sh | |
after_script: | |
- ./scripts/travis/remove-key.sh | |
after_success: | |
- ./scripts/travis/testflight.sh |
Hi there!
The docker cheat sheet has moved to a Github project under https://github.com/wsargent/docker-cheat-sheet.
Please click on the link above to go to the cheat sheet.
Let's have some command-line fun with curl, [jq][1], and the [new GitHub Search API][2].
Today we're looking for:
import ij.IJ; | |
import ij.ImagePlus; | |
import ij.Macro; | |
import loci.plugins.LociExporter; | |
/** | |
* This demonstrates how to programmatically call the Bio-Formats Exporter | |
* plugin, working around ImageJ's limitation that macro-based executions must | |
* be run in a thread named with a "Run$_" prefix. There is likely a simpler way | |
* of doing it, but this solution works. |
from omero.gateway import BlitzGateway | |
import omero | |
from omero.rtypes import rstring | |
from omero_model_ProjectI import ProjectI | |
from omero_model_DatasetI import DatasetI | |
from omero_model_ProjectDatasetLinkI import ProjectDatasetLinkI | |
from omero_model_ExperimenterI import ExperimenterI | |
from omero_model_ExperimenterGroupI import ExperimenterGroupI | |
from omero_model_PermissionsI import PermissionsI | |
from omero_model_TagAnnotationI import TagAnnotationI |
One bit of feedback we've heard from some heavy users of the API is that they want to access user and repository data by ID, and not name.
GET /users/technoweenie
GET /repos/technoweenie/faraday
If you're tracking user or repository data, using a URL with a unique and unchanging ID means the application won't break if the user or repository is
#!/usr/bin/env python | |
import traceback | |
import fcntl | |
import sys | |
import os | |
try: | |
d, = sys.argv[1:] | |
except ValueError: | |
print 'Usage: %s <directory>' % sys.argv[0] |
require 'formula' | |
class TmuxIterm2 < Formula | |
url 'http://iterm2.googlecode.com/files/iTerm2-1_0_0_20121224.zip' | |
sha1 'a2ea1cb72f3cef193d929c1580ef82710bc7345b' | |
head 'git://tmux.git.sourceforge.net/gitroot/tmux/tmux' | |
depends_on 'pkg-config' => :build | |
depends_on 'libevent' |