This is a short step-by-step guide on installing ElasticSearch LogStash and Kibana Stack on a CentOS environment to gather and analyze logs.
rpm -ivh https://dl.dropboxusercontent.com/u/5756075/jdk-7u45-linux-x64.rpm
| # Usage: | |
| # source iterm2.zsh | |
| # iTerm2 window/tab color commands | |
| # Requires iTerm2 >= Build 1.0.0.20110804 | |
| # http://code.google.com/p/iterm2/wiki/ProprietaryEscapeCodes | |
| tab-color() { | |
| echo -ne "\033]6;1;bg;red;brightness;$1\a" | |
| echo -ne "\033]6;1;bg;green;brightness;$2\a" | |
| echo -ne "\033]6;1;bg;blue;brightness;$3\a" |
| #!/bin/sh | |
| #To make use of this just copy it to your path, +x it, and do git sync | |
| MAIN_BRANCH="develop" | |
| CURRENT_CHANGES=`git status --porcelain` | |
| CURRENT_BRANCH=`git symbolic-ref -q --short HEAD` | |
| if [ "$CURRENT_CHANGES" != "" ]; then | |
| git stash --include-untracked | |
| fi |
Recently CSS has got a lot of negativity. But I would like to defend it and show, that with good naming convention CSS works pretty well.
My 3 developers team has just developed React.js application with 6561 lines of CSS (and just 5 !important).
During one year of development we had 0 issues with CSS. No refactoring typos, no style leaks, no performance problems, possibly, it is the most stable part of our application.
Here are main principles we use to write CSS for modern (IE11+) browsers:
| Latency Comparison Numbers | |
| -------------------------- | |
| L1 cache reference 0.5 ns | |
| Branch mispredict 5 ns | |
| L2 cache reference 7 ns 14x L1 cache | |
| Mutex lock/unlock 25 ns | |
| Main memory reference 100 ns 20x L2 cache, 200x L1 cache | |
| Compress 1K bytes with Zippy 3,000 ns 3 us | |
| Send 1K bytes over 1 Gbps network 10,000 ns 10 us | |
| Read 4K randomly from SSD* 150,000 ns 150 us ~1GB/sec SSD |
| " | |
| " βββ βββ βββ ββββ ββββ βββββββ βββββββ | |
| " βββ βββ βββ βββββ βββββ ββββββββ ββββββββ | |
| " βββ βββ βββ βββββββββββ ββββββββ βββ | |
| " ββββ ββββ βββ βββββββββββ ββββββββ βββ | |
| " ββββββββββ βββ βββ βββ βββ βββ βββ ββββββββ | |
| " βββ βββββ βββ βββ βββ βββ βββ βββββββ | |
| " | |
| """""""""""""""""""""""""""""" |
The easiest way to get the ClamAV package is using Homebrew
$ brew install clamav
Before trying to start the clamd process, you'll need a copy of the ClamAV databases.
Create a freshclam.conf file and configure as so