AtulKsol

brew tap homebrew/versions
brew cask install java
brew search elasticsearch
brew install elasticsearch@2.3
brew services start elasticsearch@2.3

AtulKsol

Install using Homebrew:

brew tap elastic/tap # Tap elastic 
brew search elasticsearch # Will show available versions
brew install elasticsearch@2.4 # install specific version

Start ElasticSearch Server

brew services start elasticsearch@5.6

AtulKsol

Postgres on OSX with homebrew not running [tested in mac]

Fix for following issue:

$ psql
psql: could not connect to server: No such file or directory
	Is the server running locally and accepting
	connections on Unix domain socket "/tmp/.s.PGSQL.5432"?

AtulKsol

1. pg_dump is a nifty utility designed to output a series of SQL statements that describes the schema and data of your database. You can control what goes into your backup by using additional flags.
   Backup: pg_dump -h localhost -p 5432 -U postgres -d mydb > backup.sql

   Restore: psql -h localhost -p 5432 -U postgres -d mydb < backup.sql

   -h is for host.
   -p is for port.
   -U is for username.
   -d is for database.

AtulKsol

Multiple SSH Keys settings for different github account

create different public key

create different ssh key according the article Mac Set-Up Git

$ ssh-keygen -t rsa -C "your_email@youremail.com"

AtulKsol

In Rails 3

NOTE: This post now lives (and kept up to date) on my blog: http://hakunin.com/rails3-load-paths

If you add a dir directly under app/

Do nothing. All files in this dir are eager loaded in production and lazy loaded in development by default.

If you add a dir under app/something/

AtulKsol

Container's IP Address

• docker inspect CONTAINER-ID | grep IPAddress

Container IP address using docker-compose

• docker-compose ip

Stop and remove all container

• docker stop $(docker ps -a -q)
• docker rm $(docker ps -a -q)

AtulKsol

psql: FATAL: Peer authentication failed for user “postgres” (or any user)

The connection failed because by default psql connects over UNIX sockets using peer authentication, that requires the current UNIX user to have the same user name as psql. So you will have to create the UNIX user postgres and then login as postgres or use sudo -u postgres psql database-name for accessing the database (and psql should not ask for a password).

If you cannot or do not want to create the UNIX user, like if you just want to connect to your database for ad hoc queries, forcing a socket connection using psql --host=localhost --dbname=database-name --username=postgres (as pointed out by @meyerson answer) will solve your immediate problem.

But if you intend to force password authentication over Unix sockets instead of the peer method, try changing the following pg_hba.conf* line:

from