| deb http://archive.ubuntu.com/ubuntu focal main restricted universe multiverse | |
| deb-src http://archive.ubuntu.com/ubuntu focal main restricted universe multiverse | |
| deb http://archive.ubuntu.com/ubuntu focal-security main restricted universe multiverse | |
| deb-src http://archive.ubuntu.com/ubuntu focal-security main restricted universe multiverse | |
| deb http://archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse | |
| deb-src http://archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse | |
| deb http://archive.ubuntu.com/ubuntu focal-proposed main restricted universe multiverse |
Only do this if you understand the consequences: all node programs will be able to bind on ports < 1024
sudo setcap 'cap_net_bind_service=+ep' /usr/local/bin/node
Important: your node location may vary. Use which node to find it, or use it directly in the command:
Change your app.json to base-app.json and untrack the original file in your .gitignore
Then add something like
"generateConfig": "rimraf app.json && node generateConfig" to your package.json scripts, and yarn generateConfig && react-native-scripts start to scripts like "start" or any others that may need app.json generated.
Retrieve hosted zones with aws route53 list-hosted-zones then enter the zone Id below:
aws route53 list-resource-record-sets --hosted-zone-id "/hostedzone/xxxxxxxxxxx" | \
jq -r '.ResourceRecordSets[] | [.Name, .Type, (.ResourceRecords[]? | .Value), .AliasTarget.DNSName?] | @tsv'
| #!/bin/bash | |
| # Thanks to https://gist.github.com/wenzhixin/43cf3ce909c24948c6e7 | |
| # Execute this script in your home directory. Lines 17 and 21 will prompt you for a y/n | |
| # Install Oracle JDK 8 | |
| add-apt-repository ppa:webupd8team/java | |
| apt-get update | |
| apt-get install -y oracle-java8-installer | |
| apt-get install -y unzip make # NDK stuff |
Warning: These views are highly oppinated and might have some slightly incorrect facts. My experience with typescript was about 2 weeks in Node and a week in angular2.
TypeScript is implementing their own take on JavaScript. Some of the things they are writing will likely never make it in an official ES* spec either.
Technologies that have competing spec / community driven development have a history of failing; take: Flash, SilverLight, CoffeeScript, the list goes on. If you have a large code base, picking TypeScript is something your going to be living with for a long time. I can take a bet in 3 years JavaScript will still be around without a doubt.
Its also worth noting that they have built some things like module system and as soon as the spec came out they ditched it and started using that. Have fun updating!
| #!/bin/bash | |
| target_branch="production" | |
| working_tree="PATH_TO_DEPLOY" | |
| while read oldrev newrev refname | |
| do | |
| branch=$(git rev-parse --symbolic --abbrev-ref $refname) | |
| if [ -n "$branch" ] && [ "$target_branch" == "$branch" ]; then | |
| <!doctype html> | |
| <title>Site Maintenance</title> | |
| <style> | |
| body { text-align: center; padding: 150px; } | |
| h1 { font-size: 50px; } | |
| body { font: 20px Helvetica, sans-serif; color: #333; } | |
| article { display: block; text-align: left; width: 650px; margin: 0 auto; } | |
| a { color: #dc8100; text-decoration: none; } | |
| a:hover { color: #333; text-decoration: none; } | |
| </style> |