| # | |
| # Change to the directory of the specified Go package name. | |
| # | |
| gg() { | |
| paths=($(g "$@")) | |
| path_index=0 | |
| if [ ${#paths[@]} -gt 1 ]; then | |
| c=1 |
Run your gometalinter command in CI with the --json command save output to a file e.g. lint.json
go list -f '{{.Dir}}' ./... | grep -v 'vendor' | xargs gometalinter --vendored-linters --json > lint.json
Add the following to Dangerfile
# Show lint errors
This document is obsolete, all the docs for porting are now at https://github.com/mitsuhiko/pocoo-sprint-18052013
#Overview drip is an awesome command line tool that can be used to dramatically lower perceived JVM startup time. It does this by preloading an entirely new JVM process\instance and allowing you to simply use the preloaded environment. This has extraordinary results with jruby.
We reduced time to run rake environment from 13 seconds to a mere 3.5 seconds. This is actually at or near MRI 1.9.3p327 (with falcon patch) speeds!
Adding a few addition jruby options will reduce startup time even further (down to 1.69 seconds).
#Install Drip Install drip if you haven't already (see https://github.com/flatland/drip)
| describe "Dish", -> | |
| describe "constructor", -> | |
| beforeEach -> | |
| @dish = new Dish 'Sirloin Steak $18.99 mains' | |
| it "extracts title", -> | |
| (expect @dish.title).toEqual('Sirloin Steak') |
| defmodule App.Mixfile do | |
| use Mix.Project | |
| def project do | |
| [app: :app, | |
| version: "0.0.1", | |
| elixir: "~> 1.2", | |
| elixirc_paths: elixirc_paths(Mix.env), | |
| compilers: [:phoenix] ++ Mix.compilers, | |
| build_embedded: Mix.env == :prod, |
| Go Package Management | |
| interface type version | |
| type version interface { | |
| string Version() | |
| } |
| package main | |
| // #cgo CFLAGS: -x objective-c | |
| // #cgo LDFLAGS: -framework Cocoa | |
| // #import <Cocoa/Cocoa.h> | |
| // | |
| // void run() { | |
| // @autoreleasepool { |
On heroku compiles are done without environment variables. Why?
If you compile the same source code you will ge the exact same compiled app output every time.
This is determinisim. The app build is deterministic.
If you allow environment variables at build time, the output of the app is no-longer deterministic based soley on the code. You can deploy the same code and get different results.
If you are using user-env-compile your app builds are now non-deterministic.
