#Find in content files
grep -rnw '/path/to/somewhere/' -e "pattern"
#Find in content files
grep -rnw '/path/to/somewhere/' -e "pattern"
<link rel="import" href="../topeka-elements/theme.html"> | |
<link rel="import" href="../topeka-elements/topeka-resources.html"> | |
<link rel="import" href="../topeka-elements/topeka-app.html"> | |
<link rel="import" href="../topeka-elements/topeka-datasource.html"> | |
<polymer-element name="my-element"> | |
<template> | |
<style> | |
:host { |
<link rel="import" href="../cool-clock/cool-clock.html"> | |
<link rel="import" href="../core-menu/core-submenu.html"> | |
<link rel="import" href="../core-item/core-item.html"> | |
<polymer-element name="my-element"> | |
<template> | |
<style> | |
:host { | |
position: absolute; |
<link rel="import" href="../paper-calculator/paper-calculator.html"> | |
<polymer-element name="my-element"> | |
<template> | |
<style> | |
:host { | |
position: absolute; | |
width: 100%; | |
height: 100%; |
# ======================== Elasticsearch Configuration ========================= | |
# | |
# NOTE: Elasticsearch comes with reasonable defaults for most settings. | |
# Before you set out to tweak and tune the configuration, make sure you | |
# understand what are you trying to accomplish and the consequences. | |
# | |
# The primary way of configuring a node is via this file. This template lists | |
# the most important settings you may want to configure for a production cluster. | |
# | |
# Please consult the documentation for further information on configuration options: |
lsof -iTCP -sTCP:LISTEN
$OPENSHIFT_DATA_DIR/elasticsearch/bin/elasticsearch > $OPENSHIFT_DIY_LOG_DIR/server.log 2>&1 &
http://f18-lopesale.rhcloud.com/_cluster/health?pretty=true
export JAVA_HOME=/etc/alternatives/java_sdk_1.8.0 export PATH=$JAVA_HOME/bin:$PATH
#!/bin/bash | |
set -e | |
GVERSION="1.7" | |
GFILE="go$GVERSION.linux-amd64.tar.gz" | |
GOPATH="$HOME/go" | |
GOROOT="/usr/local/go" | |
if [ -d $GOROOT ]; then | |
echo "Installation directories already exist $GOROOT" |