washort

{
  jose = {
    buildTool = "mix";
    deps = [
      "base64url"
    ];
    fetchHex = {
      sha256 = "7946d1e5c03a76ac9ef42a6e6a20001d35987afd68c2107bcd8f01a84e75aa73";
      url = "https://repo.hex.pm/tarballs/jose-1.8.4.tar";
    };

AndersonTorres

Standard project structure

This is a project structure I’ve found useful. Looking for any thoughts/comments/feedback. Roughly, I found a tension between the style nixpkgs expects and the style conducive to development, so I extracted the common portion into a derivation.nix which is used by the remaining .nix files. This setup allows me to use nix build, nix-shell, overlays, Hydra, alternate packaging schemes, cross-compiling, etc.

edolstra

Nix Flake MVP

Goals

• To provide Nix repositories with an easy and standard way to reference other Nix repositories.

• To allow such references to be queried and updated automatically.

• To provide a replacement for nix-channel, NIX_PATH and Hydra

shanesveller

{ mkDerivation }:

mkDerivation rec {
  version = "1.7.2";

  # nixnix-prefetch-url --unpack https://github.com/elixir-lang/elixir/archive/v1.7.2.tar.gz
  sha256 = "0wnrx6wlpmr23ypm8za0c4dl952nj4rjylcsdzz0xrma92ylrqfq";
  minimumOTPVersion = "18";
}

ageis

YubiKey 4 series GPG and SSH setup guide

Written for fairly adept technical users, preferably of Debian GNU/Linux, not for absolute beginners.

You'll probably be working with a single smartcard, so you'll want only one primary key (1. Sign & Certify) and two associated subkeys (2. Encrypt, 3. Authenticate). I've published a Bash function which automates this slightly special key generation process.

robertpainsi

Commit Message Guidelines

Short (72 chars or less) summary

More detailed explanatory text. Wrap it to 72 characters. The blank
line separating the summary from the body is critical (unless you omit
the body entirely).

Write your commit message in the imperative: "Fix bug" and not "Fixed
bug" or "Fixes bug." This convention matches up with commit messages

chrismccord

If you want a run-down of the 1.3 changes and the design decisions behidn those changes, check out the LonestarElixir Phoenix 1.3 keynote: https://www.youtube.com/watch?v=tMO28ar0lW8

To use the new phx.new project generator, you can install the archive with the following command:

$ mix archive.install https://github.com/phoenixframework/archives/raw/master/phx_new.ez

Bump your phoenix dep

Phoenix v1.3.0 is a backwards compatible release with v1.2.x. To upgrade your existing 1.2.x project, simply bump your phoenix dependency in mix.exs:

desmondhume

defmodule URL do
  def to_query(input, namespace) do
    Enum.map(input, fn({key, value}) -> parse("#{namespace}[#{key}]",value)end) 
    |> Enum.join("&")
  end

  def to_query(input) do
    Enum.map(input, fn({key, value}) -> parse(key,value) end)
    |> Enum.join("&")
  end

sigma

{ pkgs ? import <nixpkgs> {} }:

with pkgs;
let

  su_exec = pkgs.stdenv.mkDerivation {
    name = "su-exec-0.2";
    src = fetchurl {
      url = https://github.com/ncopa/su-exec/archive/v0.2.tar.gz;
      sha256 = "09ayhm4w7ahvwk6wpjimvgv8lx89qx31znkywqmypkp6rpccnjpc";

robphoenix

This is unmaintained, please visit Ben-PH/spacemacs-cheatsheet

Useful Spacemacs commands

• SPC q q - quit
• SPC w / - split window vertically
• SPC w - - split window horizontally
• SPC 1 - switch to window 1
• SPC 2 - switch to window 2
• SPC w c - delete current window