People
 :bowtie: |
😄 :smile: |
😆 :laughing: |
|---|---|---|
😊 :blush: |
😃 :smiley: |
:relaxed: |
😏 :smirk: |
😍 :heart_eyes: |
😘 :kissing_heart: |
😚 :kissing_closed_eyes: |
😳 :flushed: |
😌 :relieved: |
😆 :satisfied: |
😁 :grin: |
😉 :wink: |
😜 :stuck_out_tongue_winking_eye: |
😝 :stuck_out_tongue_closed_eyes: |
😀 :grinning: |
😗 :kissing: |
😙 :kissing_smiling_eyes: |
😛 :stuck_out_tongue: |
| #!/bin/bash | |
| echo "Roblox Installer by blan.ks and proofread with cleaned up code by killertofus" | |
| echo "Before the installation continues I heavily encourage you to read through the script and ensure it is not malicious" | |
| sleep 5 | |
| if grep avx /proc/cpuinfo 1>/dev/null | |
| then | |
| echo "you computer meets the requirements to play roblox" | |
| else | |
| echo "Sadly your computer is too old to play ROBLOX! With the release of Hyperion/Byfron anticheat brought requirements that your computer does not meet. (Missing AVX)" && exit |
This post was adapted from an earlier Twitter thread.
It's incredible how many collective developer hours have been wasted on pushing through the turd that is ES Modules (often mistakenly called "ES6 Modules"). Causing a big ecosystem divide and massive tooling support issues, for... well, no reason, really. There are no actual advantages to it. At all.
It looks shiny and new and some libraries use it in their documentation without any explanation, so people assume that it's the new thing that must be used. And then I end up having to explain to them why, unlike CommonJS, it doesn't actually work everywhere yet, and may never do so. For example, you can't import ESM modules from a CommonJS file! (Update: I've released a module that works around this issue.)
And then there's Rollup, which apparently requires ESM to be u
| --- | |
| # Page meta info, like heading, footer text and nav links | |
| pageInfo: | |
| title: Dashy | |
| description: Welcome to your new dashboard! | |
| navLinks: | |
| - title: GitHub | |
| path: https://github.com/Lissy93/dashy | |
| - title: Documentation | |
| path: https://dashy.to/docs |
| #!/usr/bin/env bash | |
| set -Eeuo pipefail | |
| trap cleanup SIGINT SIGTERM ERR EXIT | |
| script_dir=$(cd "$(dirname "${BASH_SOURCE[0]}")" &>/dev/null && pwd -P) | |
| usage() { | |
| cat <<EOF | |
| Usage: $(basename "${BASH_SOURCE[0]}") [-h] [-v] [-f] -p param_value arg1 [arg2...] |
Running your ASP.NET Core (or other) application in Docker using SSL should not be an overwhelming task. These steps should do the trick.
Run the following steps from a Linux terminal (I used WSL or WSL2 on Windows from the Windows Terminal).
It should look something like the content below; call it my-site.conf or something like that.
| docker stats --format "table {{.Container}}\t{{.Name}}\t{{.CPUPerc}}\t{{.MemUsage}}\t{{.MemPerc}}\t" | |
| # docker stats formatting | |
| # .Container Container name or ID (user input) | |
| # .Name Container name | |
| # .ID Container ID | |
| # .CPUPerc CPU percentage | |
| # .MemUsage Memory usage | |
| # .NetIO Network IO | |
| # .BlockIO Block IO |
| #!/bin/bash | |
| # Usage | |
| # $ ./install-cert-macos.sh "/path/to/cert" | |
| CERT_PATH="$1" | |
| # First, grab the SHA-1 from the provided SSL cert. | |
| CERT_SHA1=$(openssl x509 -in "$CERT_PATH" -sha1 -noout -fingerprint | cut -d "=" -f2 | sed "s/://g") | |
| # Next, grab the SHA-1s of any standard.dev certs in the keychain. | |
| # Don't return an error code if nothing is found. |
| alias dcp='docker-compose -f /opt/docker-compose.yml ' | |
| alias dcpull='docker-compose -f /opt/docker-compose.yml pull --parallel' | |
| alias dcplogs='docker-compose -f /opt/docker-compose.yml logs -tf --tail="50" ' | |
| alias df='df -h -x aufs -x tmpfs -x udev' | |
| alias editle='sudo vi /opt/appdata/letsencrypt/nginx/site-confs/default' |