See https://github.com/traefikturkey/onvoy/tree/master/proxmox for latest versions of the proxmox install scripts!
| #!/bin/bash | |
| # curl -s https://gist.github.com/ilude/457f2ef2e59d2bff8bb88b976464bb91/raw/cluster_create_setup.sh?$(date +%s) > ~/bin/setup_cluster.sh; chmod +x ~/bin/setup_cluster.sh; setup_cluster.sh | |
| echo "begin cluster_create_setup.sh" | |
| export CREATE_TEMPLATE=1 #false | |
| while test $# -gt 0; do | |
| case "$1" in | |
| --template) | |
| export CREATE_TEMPLATE=0 #true |
| #!/bin/bash | |
| # | |
| # Benchmark script for SBCs (Debian or Ubuntu). | |
| # | |
| # WARNING: This script is meant to be run as the root user. | |
| # This script should never be run on a system/partition you | |
| # care about. You should only run this on a system that you | |
| # intend to use only for benchmarking and can reinstall or | |
| # re-flash easily. | |
| # |
| // Discord all events! | |
| // A quick and dirty fleshing out of the discord.js event listeners (not tested at all!) | |
| // listed here -> https://discord.js.org/#/docs/main/stable/class/Client | |
| // Learn from this, do not just copy it mofo! | |
| // | |
| // Saved to -> https://gist.github.com/koad/316b265a91d933fd1b62dddfcc3ff584 | |
| // Last Updated -> Halloween 2022 | |
| /* |
| services: | |
| kubelet: | |
| extra_args: | |
| node-status-update-frequency: 4s | |
| kube-api: | |
| extra_args: | |
| default-not-ready-toleration-seconds: 30 | |
| default-unreachable-toleration-seconds: 30 | |
| kube-controller: | |
| extra_args: |
| /** | |
| * - check symlink in depencency and devDepency | |
| * - if found, generate rn-cli-config.js | |
| * - react-native start with rn-cli-config | |
| */ | |
| const packageJson = require('./package.json'); | |
| const fs = require('fs'); | |
| const exec = require('child_process').execSync; | |
| const RN_CLI_CONFIG_NAME = `rn-cli-config-with-links.js`; |
| { fontWeight: '100' }, // Thin | |
| { fontWeight: '200' }, // Ultra Light | |
| { fontWeight: '300' }, // Light | |
| { fontWeight: '400' }, // Regular | |
| { fontWeight: '500' }, // Medium | |
| { fontWeight: '600' }, // Semibold | |
| { fontWeight: '700' }, // Bold | |
| { fontWeight: '800' }, // Heavy | |
| { fontWeight: '900' }, // Black |
My current editor of choice for all things related to Javascript and Node is VS Code, which I highly recommend. The other day I needed to hunt down a bug in one of my tests written in ES6, which at time of writing is not fully supported in Node. Shortly after, I found myself down the rabbit hole of debugging in VS Code and realized this isn't as straightforward as I thought initially. This short post summarizes the steps I took to make debugging ES6 in VS Code frictionless.
My first approach was a launch configuration in launch.json mimicking tape -r babel-register ./path/to/testfile.js with babel configured to create inline sourcemaps in my package.json. The debugging started but breakpoints and stepping through the code in VS Code were a complete mess. Apparently, ad-hoc transpilation via babel-require-hook and inline sourcemaps do not work in VS Code. The same result for
attaching (instead of launch) to `babel-node
| #!/bin/bash | |
| MONGO_DATABASE="your_db_name" | |
| APP_NAME="your_app_name" | |
| MONGO_HOST="127.0.0.1" | |
| MONGO_PORT="27017" | |
| TIMESTAMP=`date +%F-%H%M` | |
| MONGODUMP_PATH="/usr/bin/mongodump" | |
| BACKUPS_DIR="/home/username/backups/$APP_NAME" |