Run this to create required files:
mkdir -p DocumentServer/{logs,data,lib}
touch gcp_service_account_credentials.json
#!/usr/bin/env bash | |
get_plist_key() { | |
local value | |
if value="$(set -o pipefail; plutil -extract "${2}" xml1 -o - "${1}" | grep -Ev "^<(\?|\!|/?plist)")"; then | |
printf "%s" "${value}" | |
fi | |
} | |
plist_status() { |
.next | |
__generated__ |
Starting a personal node project could be easy; starting a team node project could be challenging.
I am a developer currently working in SEEK Australia.
In my experience, common mistakes developer make when starting a projects are:
If we make a change, like add a property to the domain model, we have to make the same change for every use case of that model, and there could be n more use cases. We would also add m validations for that property - so one change could result in n x m changes.
version: "3.3" | |
services: | |
################################################ | |
#### Traefik Proxy Setup ##### | |
############################################### | |
traefik: | |
image: traefik:v2.0 | |
restart: always |
Use the -aes256
flag to ensure a strong passphrase protects the key:
openssl genpkey -algorithm RSA -out root.key -aes256 -pkeyopt rsa_keygen_bits:4096
// DEPRECATED! SEE https://github.com/ricealexander/eslint-config-webtrinkets for up-to-date version | |
// Some Symbols used: | |
// ⭐️ - very strong preference | |
// 🤔 - very loose preference | |
// 🔥 - disabled and would not consider enabling | |
// ⚗ - testing out a rule | |
// 💔 - could not be configured in desired way | |
// 🐝 - did not work as expected or caused clashes with other rules |