NiklasMerz

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  labels:
    app: myproject
  name: myproject
  namespace: default
spec:
  progressDeadlineSeconds: 600
  replicas: 1

nikallass

#!/bin/bash

# update apt-get
export DEBIAN_FRONTEND="noninteractive"
sudo apt-get update

# remove previously installed Docker
sudo apt-get remove docker docker-engine docker.io* lxc-docker*

# install dependencies 4 cert

garybernhardt

This document has moved!

It's now here, in The Programmer's Compendium. The content is the same as before, but being part of the compendium means that it's actively maintained.

ryanflorence

Folder Structure

Please note

While this gist has been shared and followed for years, I regret not giving more background. It was originally a gist for the engineering org I was in, not a "general suggestion" for any React app.

Typically I avoid folders altogether. Heck, I even avoid new files. If I can build an app with one 2000 line file I will. New files and folders are a pain.

guipdutra

 - => Things to do to learn the subject
 * => Tasks to complete these things
 _ok_ => Tasks completed
 CH => Chapter

Functional Programming
  - Read book Programming Clojure
    * End to read the chapter 4.
    * Read CH 5
    * Read CH 6

bltavares

Exemplo que a comunidade do #haskell é linda - https://gist.github.com/quchen/5280339

IDE’s

• Intellij (Scala) - https://confluence.jetbrains.com/display/SCA/Scala+Plugin+for+IntelliJ+IDEA
• Cursive (Clojure) - https://cursiveclojure.com/
• Intellij Haskforce (Haskell) - http://carymrobbins.github.io/intellij-haskforce/

Posts

• Conteudo sobre clojure - https://gist.github.com/bltavares/c5c2fe63ccf7a1794dbe

evancz

Architecture in Elm

This document is a collection of concepts and strategies to make large Elm projects modular and extensible.

We will start by thinking about the structure of signals in our program. Broadly speaking, your application state should live in one big foldp. You will probably merge a bunch of input signals into a single stream of updates. This sounds a bit crazy at first, but it is in the same ballpark as Om or Facebook's Flux. There are a couple major benefits to having a centralized home for your application state:

1. There is a single source of truth. Traditional approaches force you to write a decent amount of custom and error prone code to synchronize state between many different stateful components. (The state of this widget needs to be synced with the application state, which needs to be synced with some other widget, etc.) By placing all of your state in one location, you eliminate an entire class of bugs in which two components get into inconsistent states. We also think yo

Kartones

PSQL

Magic words:

psql -U postgres

Some interesting flags (to see all, use -h or --help depending on your psql version):

• -E: will describe the underlaying queries of the \ commands (cool for learning!)
• -l: psql will list all databases and then exit (useful if the user you connect with doesn't has a default database, like at AWS RDS)

jodosha

source 'https://rubygems.org'

gem 'rake'
gem 'lotus-router'
gem 'lotus-controller'
gem 'lotus-view'

group :test do
  gem 'rspec'
  gem 'capybara'

lelandbatey

Description

This simple script will take a picture of a whiteboard and use parts of the ImageMagick library with sane defaults to clean it up tremendously.

The script is here:

#!/bin/bash
convert "$1" -morphology Convolve DoG:15,100,0 -negate -normalize -blur 0x1 -channel RBG -level 60%,91%,0.1 "$2"

Results