- Create a folder at the root of your user home folder
(Example:
C:/Users/uname/) called.ssh. - Create the following files if they do not already exist (paths begin from the root of your user home folder):
.ssh/config
| 1="Unsupported protocol. This build of curl has no support for this protocol." | |
| 2="Failed to initialize." | |
| 3="URL malformed. The syntax was not correct." | |
| 4="A feature or option that was needed to perform the desired request was not enabled or was explicitly disabled at build-time. To make curl able to do this, you probably need another build of libcurl!" | |
| 5="Couldn't resolve proxy. The given proxy host could not be resolved." | |
| 6="Couldn't resolve host. The given remote host was not resolved." | |
| 7="Failed to connect to host." | |
| 8="Weird server reply. The server sent data curl couldn't parse." | |
| 9="FTP access denied. The server denied login or denied access to the particular resource or directory you wanted to reach. Most often you tried to change to a directory that doesn't exist on the server." | |
| 10="FTP accept failed. While waiting for the server to connect back when an active FTP session is used, an error code was sent over the control connection or similar." |
| ##TCP FLAGS## | |
| Unskilled Attackers Pester Real Security Folks | |
| ============================================== | |
| TCPDUMP FLAGS | |
| Unskilled = URG = (Not Displayed in Flag Field, Displayed elsewhere) | |
| Attackers = ACK = (Not Displayed in Flag Field, Displayed elsewhere) | |
| Pester = PSH = [P] (Push Data) | |
| Real = RST = [R] (Reset Connection) | |
| Security = SYN = [S] (Start Connection) |
| # Add the following 'help' target to your Makefile | |
| # And add help text after each target name starting with '\#\#' | |
| help: ## Show this help. | |
| @fgrep -h "##" $(MAKEFILE_LIST) | fgrep -v fgrep | sed -e 's/\\$$//' | sed -e 's/##//' | |
| # Everything below is an example | |
| target00: ## This message will show up when typing 'make help' | |
| @echo does nothing |
| #!/bin/bash | |
| module=$1 | |
| for resource in `terraform show -module-depth=1 | grep module.${module} | tr -d ':' | sed -e 's/module.${module}.//'`; do | |
| terraform taint -module ${module} ${resource} | |
| done |
| #!/bin/bash | |
| # This script creates a docker config.json file with the auth section | |
| # as an example of what can be passed into GitLab-CI and used in | |
| # conjunction with DOCKER_CONFIG - the config file directory location. | |
| # command line parameter default values | |
| DOCKER_REGISTRY="" | |
| DOCKER_USER="" | |
| DOCKER_PASSWORD="" |
| #!/bin/bash | |
| set -e | |
| if [ $# -eq 0 ]; then | |
| echo "USAGE: $0 plugin1 plugin2 ..." | |
| exit 1 | |
| fi | |
| plugin_dir=/var/lib/jenkins/plugins |
This is a step by step instruction on how to create a cluster that has three Solr nodes running in cloud mode. These instructions should work on both a local cluster (for testing) and a remote cluster where each server runs in its own physical machine.
This was tested on Solr version 5.4.1 and Zookeeper version 3.4.6
curl -O http://archive.apache.org/dist/lucene/solr/5.5.3/solr-5.5.3.tgzmkdir /opt/solrAn IAM user policy document to give minimal rights for deploying an Elastic Beanstalk application.
Where:
REGION: AWS region.ACCOUNT_ID: AWS account ID.APPLICATION_NAME: Desired target Elastic Beanstalk application name(space).IAM_INSTANCE_PROFILE_ROLE: The instance profile (IAM role) Elastic Beanstalk EC2 instaces will run under.| #!/bin/bash | |
| # Use whichever region you're working in | |
| export AWS_DEFAULT_REGION=eu-west-1 | |
| # Make ec2-user's home dir the install to make it easier to navigate when subsequently ssh-ing in to instances | |
| su ec2-user - | |
| cd /home/ec2-user | |
| echo Working dir is `pwd` |