#GIT
- Modificado (modified);
- Preparado (staged/index)
- Consolidado (comitted);
Best UNIX Shell tools | |
These are a list of usages of shell commands I can't live without on UNIX-based systems. | |
Install | |
Mac OS X | |
Using Homebrew (yes, I am opinionated) you can install the following tools with the following packages: | |
brew install proctools # to install pgrep, pkill, etc. | |
brew install pstree # to be able to use pstree | |
brew install vnstat # to be able to use vnstat |
#http://pastebin.com/xGt6vv9R from yardenbar | |
output { | |
if [type] == "postfix" { | |
elasticsearch { | |
host => [ "ES_HOSTNAME" ] | |
protocol => "transport" | |
cluster => "elasticsearch" | |
index => "postfix-%{+YYYY.MM.dd}" | |
manage_template => true | |
template_overwrite => true |
--- | |
client: | |
hosts: | |
- "es_coordinating_01.singhaiuklimited.com" | |
port: 9200 | |
url_prefix: | |
use_ssl: True | |
# The certificate file is the CA certificate used to sign all ES node certificates. | |
# Use same CA certificate to generate and sign the certificate running curator (specified in properties client_cert and client_key) | |
certificate: '/work/elk/elasticsearch-6.3.2/config/x-pack/certificate-bundle/ca/ca.crt' |
Scalable, elastic, cloud-native NFS file system
You can create a launch template that contains the configuration information to launch an instance. Launch templates enable you to store launch parameters so that you do not have to specify them every time you launch an instance. For example, a launch template can contain the AMI ID, instance type, and network settings that you typically use to launch instances. When you launch an instance using the Amazon EC2 console, an AWS SDK, or a command line tool, you can specify the launch template to use.
The following diagram shows a launch template with three versions.
Elastic Load Balancing automatically distributes your incoming traffic across multiple targets, such as EC2 instances, containers, and IP addresses, in one or more Availability Zones. It monitors the health of its registered targets, and routes traffic only to the healthy targets. Elastic Load Balancing scales your load balancer as your incoming traffic changes over time. It can automatically scale to the vast majority of workloads.
Elastic Load Balancing supports the following load balancers: Application Load Balancers, Network Load Balancers, Gateway Load Balancers, and Classic Load Balancers.
The following diagram illustrates the basic components. Notice that each listener contains a default rule, and one listener contains another rule that routes requests to a different target group. One target is registered with two target groups.
Let Tomcat is download and installed under /opt/tomcat
.
Also, let tomcat
be a non-provileged user under which the server will be running.
We assume that we keep server's binaries under /opt/tomcat
and we will create a server instance named foo
under /var/tomcat/
(carrying its own conf
, logs
, webapps
, work
, lib
directories).
See also https://dzone.com/articles/running-multiple-tomcat.
Create a template service unit file at /etc/systemd/system/[email protected]
:
# ##################################################################### | |
# DESC: Logstash configuration file. Typically forwarding logs to | |
# Elasticsearch instance. | |
# ##################################################################### | |
# Where to get input | |
input { | |
# Get input from standard input device/interface | |
stdin { | |
type => "stdin-type" |
# ##################################################################### | |
# DESC: Logstash configuration file. Typically forwarding logs to | |
# Elasticsearch instance. | |
# ##################################################################### | |
# Where to get input | |
input { | |
# Get input from standard input device/interface | |
stdin { | |
type => "stdin-type" |