Try-Try-Again

$ git remote rm origin
$ git remote add origin git@github.com:aplikacjainfo/proj1.git
$ git config master.remote origin
$ git config master.merge refs/heads/master

Try-Try-Again

# vim: ft=cfg
#
# This is the configuration file of "rifle", ranger's file executor/opener.
# Each line consists of conditions and a command.  For each line the conditions
# are checked and if they are met, the respective command is run.
#
# Syntax:
#   <condition1> , <condition2> , ... = command
#
# The command can contain these environment variables:

Try-Try-Again

React makes compositing components easy. However testing them can get ugly if you are not careful. Consider this example:

var ChildA = React.createClass({
    displayName: "ChildA",
    render: function(){
        return (<div>A in the house</div>);
    }
});

Try-Try-Again

/*******************************************************************************
*
* A minimal Forth compiler in C
* By Leif Bruder <leifbruder@gmail.com> http://defineanswer42.wordpress.com
* Release 2014-04-04
*
* Based on Richard W.M. Jones' excellent Jonesforth sources/tutorial
*
* PUBLIC DOMAIN
*

Try-Try-Again

Working with ansible-vault

---

I've been using a lot of Ansible lately and while almost everything has been great, finding a clean way to implement ansible-vault wasn't immediately apparent.

What I decided on was the following: put your secret information into a vars file, reference that vars file from your task, and encrypt the whole vars file using ansible-vault encrypt.

Let's use an example: You're writing an Ansible role and want to encrypt the spoiler for the movie Aliens.

Try-Try-Again

Updating a feature branch

First we'll update your local master branch. Go to your local project and check out the branch you want to merge into (your local master branch)

$ git checkout master

Fetch the remote, bringing the branches and their commits from the remote repository. You can use the -p, --prune option to delete any remote-tracking references that no longer exist in the remote. Commits to master will be stored in a local branch, remotes/origin/master

Try-Try-Again

Proxy Performance:
Proxy Server Currently has reponse time of < 15ms with 0% error rate (New Relic) 
for tests of 1 rps, 10 rps, and 100 rps

1000 rps test fails with 52.8 % error rate and response time of approx 150 ms

Service Performance:
API calls to service has response time of < 10ms with 0% error rate (New Relic)
for tests of 1 rps, 10 rps, and 100 rps

Try-Try-Again

# 1 RPS
All virtual users finished
Summary report @ 21:25:07(-0800) 2020-02-23
  Scenarios launched:  60
  Scenarios completed: 60
  Requests completed:  60
  RPS sent: 1.01
  Request latency:
    min: 2.2
    max: 24.1

Try-Try-Again

# 1 RPS
All virtual users finished
Summary report @ 16:04:02(-0800) 2020-02-23
  Scenarios launched:  60
  Scenarios completed: 60
  Requests completed:  60
  RPS sent: 1.01
  Request latency:
    min: 2.7
    max: 23

Try-Try-Again

PostgreSQL: 

ryan=# select * from photos where experienceid = 1000 LIMIT 1;
 photoid |                    photourl                     |    alt     | username | experienceid 
---------+-------------------------------------------------+------------+----------+--------------
   11001 | https://rybnb.s3-us-west-1.amazonaws.com/40.jpg | Automotive | Alvena   |         1000
(1 row)

Time: 15.333 ms