Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.
| let regex; | |
| /* matching a specific string */ | |
| regex = /hello/; // looks for the string between the forward slashes (case-sensitive)... matches "hello", "hello123", "123hello123", "123hello"; doesn't match for "hell0", "Hello" | |
| regex = /hello/i; // looks for the string between the forward slashes (case-insensitive)... matches "hello", "HelLo", "123HelLO" | |
| regex = /hello/g; // looks for multiple occurrences of string between the forward slashes... | |
| /* wildcards */ | |
| regex = /h.llo/; // the "." matches any one character other than a new line character... matches "hello", "hallo" but not "h\nllo" | |
| regex = /h.*llo/; // the "*" matches any character(s) zero or more times... matches "hello", "heeeeeello", "hllo", "hwarwareallo" |
This is quick howto for installing vault on AWS Amazon Linux AMI, so the setup can be replicated easily without the concerns of detailed steps on securing. At the end of this tutorial, you'll have a working vault server, using s3 for the backend, ensure the vault server is always running, and starts on reboot.
First things first, let's set up an S3 bucket to use as the storage backend for our S3 instance.
From the AWS Mangement Console, go to the S3 console.
Click on the Create Bucket button
Execute the shell script: jenkins_install.sh
Configure a proxy using nginx or apache to http://ci.company.example.com.br(I'll use this URL as example).
