desaiuditd

/**
 * Mimics PHP's ucfirst function.
 *
 * @param  subject The string to be ucfirst'd
 * @return The subject string with an uppercased first character
 */
final public static String ucfirst(String subject)
{
    return Character.toUpperCase(subject.charAt(0)) + subject.substring(1);
}

desaiuditd

Keybase proof

I hereby claim:

• I am desaiuditd on github.
• I am desaiuditd (https://keybase.io/desaiuditd) on keybase.
• I have a public key whose fingerprint is 2C76 0DDF EAF3 3C66 B687 FCFB 7F21 FD23 2244 74F5

To claim this, I am signing this object:

desaiuditd

server {


    server_name example.com   www.home.example.com;


    access_log /var/log/nginx/example.com.access.log ; 
    error_log /var/log/nginx/example.com.error.log;

desaiuditd

docker run \
 --rm \
 --link mongodb:mongo \
 -v /home/ubuntu/backup-dir:/backup \
 mongo \
 bash -c ‘mongodump --out /backup --host $MONGO_PORT_27017_TCP_ADDR’

desaiuditd

The workflow says that the master branch of a project is the golden branch from which all development is based off of.

In order to keep this easy to navigate, it is asked that you squash your commits down to a few, or one, discreet changesets before submitting a pull request. Fixing a bug will usually only need one commit, while a larger feature might contain a couple of separate improvements that is easier to track through different commits.

Once you have rebased your work on top of the latest state of the upstream master, you may have several commits related to the issue you were working on. Once everything is done, squash them into a single commit with a descriptive message, like "Issue #100: Retweet bugfix."

desaiuditd

-ea
-server
-Xms2g
-Xmx1g
-Xss16m
-XX:PermSize=256m
-XX:MaxPermSize=1024m
-XX:+DoEscapeAnalysis
-XX:+UseCompressedOops
-XX:+UnlockExperimentalVMOptions

desaiuditd

Let's say, 5 commits are made in develop branch.

• Commit 4 => 2017/06/23
• Commit 3 => 2017/06/22
• Commit 2 => 2017/06/21
• Commit 1 => 2017/06/20

Now we want to squash these commits into one commit (i.e., the latest commit on 2017/06/23).

git rebase -i HEAD~4

desaiuditd

Install EasyEngine (HTTP Proxy Server)

wget -qO ee rt.cx/ee && sudo bash ee

Install NVM

curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.4/install.sh | bash

desaiuditd

To remove a submodule you need to:

• Delete the relevant section from the .gitmodules file.
• Stage the .gitmodules changes git add .gitmodules
• Delete the relevant section from .git/config.
• Run git rm --cached path_to_submodule (no trailing slash).
• Run rm -rf .git/modules/path_to_submodule (no trailing slash).
• Commit git commit -m "Removed submodule "
• Delete the now untracked submodule files rm -rf path_to_submodule

desaiuditd

const { Component, Fragment } = wp.element;

// This is going to add block controls to switch the state between preview and search.
import ItemControls from './controls';
// Preview is going to show users how items are going to look like.
import Preview from './preview';
// Search is allowing to search for items.
import Search from './search';

/**