Moved to https://ftvdb.com
| async function readRequestBody(request) { | |
| const { headers } = request; | |
| const contentType = headers.get('content-type') || ''; | |
| if (contentType.includes('application/json')) { | |
| return JSON.stringify(await request.json()); | |
| } else if (contentType.includes('form')) { | |
| const formData = await request.formData(); | |
| const body = {}; | |
| for (const entry of formData.entries()) { | |
| body[entry[0]] = entry[1]; |
| <?php | |
| /** | |
| ----------------------------------------------------- | |
| Enforce the Laravel Code Style using PHP CS Fixer 3.x | |
| ----------------------------------------------------- | |
| Credits go to Laravel Shift & Andreas Elia. | |
| https://gist.github.com/laravel-shift/cab527923ed2a109dda047b97d53c200 | |
| /** | |
| * Copy rich text content to clipboard. | |
| * | |
| * Must be initiated by a user click event. | |
| * | |
| * @param {string} content | |
| */ | |
| export default function (content) { | |
| const selection = window.getSelection(); |
I am writing this guide becuase I coudn't find a proper one online which contained all the information I was searching for. I will try to guide you through the process of enabling link aggregation (802.3ad) with your Ubiquiti hardware and your Unraid server. Note: not all of Ubiquiti's hardware supports link aggregation (LAG). As of the time of writing Ubiquiti states the following.
Applicable to all UniFi Switch models excluding the USW-Flex and USW-Flex-Mini.
Source: Ubiquiti
| #!/bin/bash | |
| APP_DIR=$1 | |
| APP_SCRIPT_NAME="$(ls "${APP_DIR}/Contents/MacOS/")" | |
| APP_FILE_NAME="$(basename "${APP_DIR}")" | |
| CHANNEL_DIR="$(dirname "$(dirname "$1")")" | |
| CHANNEL_NAME="$(basename "$CHANNEL_DIR")" | |
| TOOLBOX_APP_NAME="$(basename "$(dirname "$CHANNEL_DIR")")" |
This is an initiative to create an overview of the issues found with the Creality CR-6 SE.
As of this writing (2020-09-19) the large number of the motherboard issues have not been publicly acknowledged. Hopefully this overview forces Creality to acknowledge the issues with the Creality CR-6 SE leveling free 3d printer.
According to Creality all issues should be resolved in the newer models:
Here are the improvements we did as below:
| opendb () { | |
| [ ! -f .env ] && { echo "No .env file found."; exit 1; } | |
| DB_CONNECTION=$(grep DB_CONNECTION .env | grep -v -e '^\s*#' | cut -d '=' -f 2-) | |
| DB_HOST=$(grep DB_HOST .env | grep -v -e '^\s*#' | cut -d '=' -f 2-) | |
| DB_PORT=$(grep DB_PORT .env | grep -v -e '^\s*#' | cut -d '=' -f 2-) | |
| DB_DATABASE=$(grep DB_DATABASE .env | grep -v -e '^\s*#' | cut -d '=' -f 2-) | |
| DB_USERNAME=$(grep DB_USERNAME .env | grep -v -e '^\s*#' | cut -d '=' -f 2-) | |
| DB_PASSWORD=$(grep DB_PASSWORD .env | grep -v -e '^\s*#' | cut -d '=' -f 2-) |
With most of the CR-6 SE issues being due to bad wiring or loose/too tight screws I feel like it is time for a good post-unboxing checklist, to be walked through pre-assembly. Even though I do not have my unit shipped yet, I've seen enough issues and fixes that I can compile this post.
I initially posted this on the independent CR-6 community Facebook group but since not everyone wants to use Facebook (which I totally understand), I will repost it here. I mirrored most of the relevant content of Facebook to imgur.
If you have any feedback or anything that needs to be added, please let me know and I will amend this post!
Note: There are some known issues with this printer - please read the entire guide. (It is long, I know, but this is a necessary evil!)
| <?php | |
| Artisan::command('db:open {connection?}', function ($connection = null) { | |
| if (! file_exists('/Applications/TablePlus.app')) { | |
| $this->warn('This command uses TablePlus, are you sure it\'s installed?'); | |
| $this->line("Install here: https://tableplus.com/\n"); | |
| } | |
| $driver = $connection ?: config('database.default'); | |
| $host = config("database.connections.{$driver}.host"); |