This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| how will this render? ❤ |
This is an excerpt from an internal discussion at Park Assist on 2016-07-08:
Me:
April and I are pairing up on an effort to… and we felt that we should use a system to track the work, but we were loath to use JIRA. So we’re trying out Clubhouse. I’m going to send everyone an invite; feel free to poke around, try it out, etc.
Ilan Goodman:
On my first pass, it seems very similar to JIRA right out of the box. Can you elaborate on what you dislike about JIRA and why Clubhouse might be better?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| (ns image-diff | |
| "Most of this is ported from https://rosettacode.org/wiki/Percentage_difference_between_images#Java" | |
| (:import [java.awt Color] | |
| [java.awt.image BufferedImage])) | |
| (defn pixel-diff | |
| [a b] | |
| (let [a-color-components (.getRGBColorComponents (Color. a) nil) | |
| b-color-components (.getRGBColorComponents (Color. b) nil)] | |
| (->> (map - a-color-components b-color-components) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| This works from bash but I haven’t managed to get it to work from within a profile in a deps.edn file: | |
| clojure -Sdeps "{:deps {jonase/kibit {:mvn/version \"0.1.6\"}}}" -e "(require '[kibit.driver :as k]) (k/external-run [\"src\"] nil)" |
- Cognitect’s test runner for projects using tools.deps
- kibit is a static code analyzer for Clojure, ClojureScript, cljx and other Clojure variants. It uses core.logic to search for patterns of code that could be rewritten with a more idiomatic function or macro.
- Eastwood is a Clojure lint tool that uses the tools.analyzer and tools.analyzer.jvm libraries to inspect namespaces and report possible problems.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| FROM openjdk:8-alpine | |
| LABEL maintainer="Avi Flax <[email protected]>" | |
| WORKDIR /tmp | |
| RUN echo "@testing http://nl.alpinelinux.org/alpine/edge/testing" >> /etc/apk/repositories | |
| RUN apk add --update --no-cache bash curl rlwrap@testing | |
| RUN curl -O https://download.clojure.org/install/linux-install-1.9.0.315.sh | |
| RUN chmod +x linux-install-1.9.0.315.sh | |
| RUN ./linux-install-1.9.0.315.sh |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| query RecentCommitters($org: String!) { | |
| organization(login: $org) { | |
| name | |
| repositories(first: 100) { | |
| edges { | |
| node { | |
| name | |
| defaultBranchRef { | |
| target { | |
| ... on Commit { |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Originally sent in a Twitter DM to Robin Biljani. | |
| ---- | |
| Glad Irma wasn’t too catastrophic for you! | |
| I have similar feelings about Funding Circle, the technologies they’re using, social lending platforms, and the team at Park Assist 👍 | |
| OK so, that scenario sounds suspiciously like the “classic” microservice architecture. So it would be… understandable to see this as reasonable simply because it’s fairly common. The logic is something like: this seems to be working for various high-profile orgs, so why not for us? Which is understandable. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # Super CORS for NGINX | |
| # NOT YET TESTED | |
| # Based on https://enable-cors.org/server_nginx.html | |
| # which was based on https://michielkalkman.com/snippets/nginx-cors-open-configuration/ | |
| location / { | |
| # preflight | |
| if ($request_method = 'OPTIONS') { | |
| add_header 'Access-Control-Allow-Origin' "$http_origin"; # wildcard wouldn’t work with Access-Control-Allow-Credentials | |
| add_header 'Access-Control-Allow-Credentials' 'true'; |