My Elasticsearch cheatsheet with example usage via rest api (still a work-in-progress)
|# import config.|
|# You can change the default config with `make cnf="config_special.env" build`|
|cnf ?= config.env|
|export $(shell sed 's/=.*//' $(cnf))|
|# import deploy config|
|# You can change the default deploy config with `make cnf="deploy_special.env" release`|
|dpl ?= deploy.env|
Homebrew is a package management system for OS X. You can read more about it here, or simply run
ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
to install it.
|Go to Bitbucket and create a new repository (its better to have an empty repo)|
|git clone email@example.com:abc/myforkedrepo.git|
|Now add Github repo as a new remote in Bitbucket called "sync"|
|git remote add sync firstname.lastname@example.org:def/originalrepo.git|
|Verify what are the remotes currently being setup for "myforkedrepo". This following command should show "fetch" and "push" for two remotes i.e. "origin" and "sync"|
|git remote -v|
In this example, we are using
systemctl so that we can monitor logs from DC/OS instances (masters, agents and public agents). It is useful for anyone using
journald in an AWS EC2 enviroment that wants logging. The nice thing about Amazon CloudWatch is that it integrates well with Amazon EMR and Amazon Elasticsearch. (For more background on this subject see this article which covers using CloudFormation, Packr, etc. for Immutable Infrastructure to build DC/OS and deploy it to Amazon Web Services.)
We will install journald-cloudwatch-logs. We are going to setup a daemon into systemd that forwards logs to Amazon CloudWatch log streams.
This utility ***journald-cloudwat