Now where you are a collaborator you have certain powers that you should use carefully, so I'm listing some guidelines here.
Even though as a contributor you could push directly to master, please don't do that. Instead each bug fix or feature
import path from 'path' | |
// 1. Define root of project from which to resolve all packages | |
const ROOT = path.resolve(__dirname, '..') | |
// 2. Define the relative path of the package that we generate the dorny filters for | |
const PACK = process.argv[2] | |
if (PACK == null) { | |
throw new Error( | |
'Need to supply relative path argument for package you want to render dorny filter for' |
// Run as a Chrome Snippetfrom either of the below urls: | |
// https://www.jazzradio.com/member/favorite/channels | |
// https://www.classicalradio.com/member/favorite/channels | |
// https://www.radiotunes.com/member/favorite/channels | |
// https://www.rockradio.com/member/favorite/channels | |
// https://www.zenradio.com/member/favorite/channels | |
const KEY = '<yourkeyhere>' | |
const subsidy = document.location.host.split('.')[1] | |
function getChannelInfos() { |
#!/usr/bin/env bash | |
## Prepare Wallets | |
solana-keygen new --silent --no-bip39-passphrase --outfile solpair1.json | |
solana-keygen new --silent --no-bip39-passphrase --outfile solpair2.json | |
### Airdrop and label them | |
amman airdrop ./solpair1.json -l soladdr1 |
Notes for intro provided by commander_thrashdin.
(fun arg1 arg1 ...)
http://05738ef0.ngrok.io |
Table of Contents generated with DocToc
First we need to create a certificate. The llvm provided a way to do
that, but I found this
way to work slightly better for me. Just substitute
lldb_codesign
for the certificate name, instead of gdb-cert
.