bugyt

ArchLinux Cheat Sheet

Network configuration

• List network devices

    # ip link
  

• Enabling and disabling network interfaces

    # ip link set <network interface> up
  

ip link set down

rpdelaney

#    +--------- Minute (0-59)                                | Output Dumper: >/dev/null 2>&1
#    |    +------- Hour (0-23)                               | Multiple Values Use Commas: 3,12,47
#    |    |    +----- Day Of Month (1-31)                    | Do every X intervals: */X  -> Example: */15 * * * *  Is every 15 minutes
#    |    |    |    +--- Month (1 -12)                       | Aliases: @reboot -> Run once at startup; @hourly -> 0 * * * *;
#    |    |    |    |    +- Day Of Week (0-6) (Sunday = 0)   | @daily -> 0 0 * * *; @weekly -> 0 0 * * 0; @monthly ->0 0 1 * *;
#    |    |    |    |    |                                   | @yearly -> 0 0 1 1 *;
#    *    *    *    *    *     COMMAND

jessejanderson

Community

• Elixir Slack Group

Cheatsheets

• GenServer Cheatsheet by Benjamin Tan Wei Hao

Books

nicholasjhenry

GraphQL Schema Language Cheat Sheet

The definitive guide to express your GraphQL schema succinctly

A port of a cheat sheet authored by Hafiz Ismail.

What does it look like?

defmodule MyApp.Schema do
 use Absinthe.Schema

bsedat

FROM elixir:1.4.5 as asset-builder-mix-getter

ENV HOME=/opt/app

RUN mix do local.hex --force, local.rebar --force
# Cache elixir deps
COPY config/ $HOME/config/
COPY mix.exs mix.lock $HOME/
COPY apps/myproject_web/mix.exs $HOME/apps/myproject_web/
COPY apps/myproject_web/config/ $HOME/apps/myproject_web/config/

pythoninthegrass

#!/usr/bin/env bash
# SOURCE: https://eligiblestore.com/blog/2017/05/02/how-to-install-mosh-on-centos/

# ensure running as root
if [[ "$(id -u)" != "0" ]]; then
  exec sudo "$0" "$@"
fi

# install mosh
yum install -y epel-release

swalkinshaw

Moved to Shopify/graphql-design-tutorial

sub-mod

Following steps work for F29 for F31 look here

On the remote host

cat /etc/redhat-release
Fedora release 29 (Twenty Nine)

Install packages

candlerb

If someone asked me the question "what layout should I use for my Go code repository?", I'd start by asking back "what are you building: an executable, or a library?"

Single executable

Stage 1: single source file

Create a directory named however you want your final executable to be called (e.g. "mycommand"), change into that directory, and create the following files: