In your command-line run the following commands:
brew doctor
brew update
#Add ENV strings into AWS Parameter Store (as one parameter). All strings will be separated by the newline | |
#We are getting ENV string separated by the newline and pub them in the dotenv | |
aws ssm get-parameter --name Param-with-env --region eu-west-1 --query Parameter.Value | sed -e 's/^"//' -e 's/"$//' | awk '{gsub(/\\n/,"\n")}1' >> .env |
In your command-line run the following commands:
brew doctor
brew update
<?php | |
/** | |
* This method logically validates Turkish VAT number | |
* | |
* @param string $taxNumber | |
* @return bool | |
*/ | |
public function validateTaxNumber(string $taxNumber): bool | |
{ |
cd ~/ | |
mkdir .localhost-ssl | |
sudo openssl genrsa -out ~/.localhost-ssl/localhost.key 2048 | |
sudo openssl req -new -x509 -key ~/.localhost-ssl/localhost.key -out ~/.localhost-ssl/localhost.crt -days 3650 -subj /CN=localhost | |
sudo security add-trusted-cert -d -r trustRoot -k /Library/Keychains/System.keychain ~/.localhost-ssl/localhost.crt | |
npm install -g http-server | |
echo " | |
function https-server() { |
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.
{ | |
"require": { | |
"mfacenet/hello-world": "v1.*" | |
} | |
} |
.
├── index.ios.js
├── js
│ ├── actions
│ │ ├── ChatServerActionCreators.js
│ │ └── ChatThreadActionCreators.js
│ ├── components
│ │ ├── ChatScreen
│ │ │ ├── index.js
fa-glass | |
fa-music | |
fa-search | |
fa-envelope-o | |
fa-heart | |
fa-star | |
fa-star-o | |
fa-user | |
fa-film | |
fa-th-large |
/** | |
* Fancy ID generator that creates 20-character string identifiers with the following properties: | |
* | |
* 1. They're based on timestamp so that they sort *after* any existing ids. | |
* 2. They contain 72-bits of random data after the timestamp so that IDs won't collide with other clients' IDs. | |
* 3. They sort *lexicographically* (so the timestamp is converted to characters that will sort properly). | |
* 4. They're monotonically increasing. Even if you generate more than one in the same timestamp, the | |
* latter ones will sort after the former ones. We do this by using the previous random bits | |
* but "incrementing" them by 1 (only in the case of a timestamp collision). | |
*/ |