micalevisk

Articles         █████████████▋░░░░░░░  65.1%
Videos           ██████████████████▌░░  88.3%
Books            ████████▋░░░░░░░░░░░░  41.4%
Learn React      ████████████░░░░░░░░░  57.1%
Learn TypeScript █████████████████████ 100.0%
GitHub           ████████████████▊░░░░  80.0%

jcollins-g

<!-- Copyright 2011 the Dart project authors. All rights reserved.
     Use of this source code is governed by a BSD-style license
     that can be found in the LICENSE file. -->

<h2>Dr. Fibonacci's Sunflower Spectacular</h2>

<div>
  <canvas id="canvas" width="300" height="300"></canvas>
</div>

nelsonic

On Mar 28, 2013 Dan Allen explained how to deploy to github-pages automatically. Many other GitHub users like Steve Klabnik and Domenic Denicola followed with the same approach:

Use an OAuth token with public_repo or repo permission to access the Github account over HTTPS inside a virtual build environment.

The same applies to Travis CI's built-in abilities, and there are more restrictions as deploying GitHub Releases works only for tags, not for branches.

Security concerns

The token grants write access for all of your (public) repositories and

booleangate

Salesforce OAuth 2.0 JWT Bearer Token Flow Walk-Through

This document will walk you through how to create or configure a Salesforce application for use with JWT authentication. These configuration steps and the example code works as of Salesforce API version 42.0.

Prerequisites

Create an RSA x509 private key/certification pair

zulhfreelancer

$ cd ~/Library/Application\ Support/Postgres/var-10
$ \rm -f postmaster.pid

OR

$ \rm -f ~/Library/Application\ Support/Postgres/var-10/postmaster.pid

scottashipp

# from https://codeburst.io/how-i-hacked-my-terminal-so-a-happy-whale-would-spout-software-quotes-at-me-6791e6c74fc6

%
Simple things should be simple, complex things should be possible.
  The Wiki Way: Quick Collaboration on the Web, Bo Leuf, Ward
  Cunningham
%
Simplicity is the soul of efficiency.
  Austin Freeman
%

deepanprabhu

let params = {
  TableName:  'xxx',
  Limit: 50 // Configure based on needs
};
let aItems = [];
const recursiveScan = (params) => {
    return client.scan(params).promise().then((data) => {
        //  Simple Changes to input, optional
        let newItems = data.Items.map((item) => {
            return item;

evancz

A vision for data interchange in Elm

How do you send information between clients and servers? What format should that information be in? What happens when the server changes the format, but the client has not been updated yet? What happens when the server changes the format, but the database cannot be updated?

These are difficult questions. It is not just about picking a format, but rather picking a format that can evolve as your application evolves.

Literature Review

By now there are many approaches to communicating between client and server. These approaches tend to be known within specific companies and language communities, but the techniques do not cross borders. I will outline JSON, ProtoBuf, and GraphQL here so we can learn from them all.

letmaik

If you want to use travis_retry from within your own shell script files then you first have to make the travis_retry shell function available by sourcing the travis_retry.sh file, otherwise you just get a "command not found" error. See example.sh for a full example.

Note that the original function as found in the travis-ci/travis-build repository was slightly modified to allow it to be used in a shell context where set -e is enabled.

For reference, a tweet by Travis CI saying that you should copy the travis_retry code as I've done here: https://twitter.com/plexus/status/499194992632811520

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: