In your command-line run the following commands:
brew doctorbrew update
In your command-line run the following commands:
brew doctorbrew updateUpdate: As of 11 January 2022, git.io no longer accepts new URLs.
Command:
curl https://git.io/ -i -F "url=https://github.com/YOUR_GITHUB_URL" -F "code=YOUR_CUSTOM_NAME"URLs that can be created is from:
https://github.com/*https://*.github.com| #!/bin/bash | |
| # Instal php5.6 with phpbrew on ubuntu 18.04 | |
| # Install all dependencies | |
| sudo apt update | |
| sudo apt install wget php build-essential libxml2-dev libxslt1-dev libbz2-dev libcurl4-openssl-dev libmcrypt-dev libreadline-dev libssl-dev autoconf | |
| wget https://github.com/phpbrew/phpbrew/raw/master/phpbrew | |
| chmod +x phpbrew | |
| mv phpbrew /usr/local/bin |
| #!/bin/bash | |
| echo 'update brew' | |
| brew update | |
| echo 'upgrade brew' | |
| brew upgrade |
laravel 無疑是 php 世界裡最主流的框架,但有使用 laravel 的人都知道,每一條 request 進來要 import 許多的 class 一直是 laravel 的痛,這也導致他在高併發底下表現不甚理想。
而 laravel 作者為了解決這個問題,開發使用 swoole 或 roadrunner 做基底的套件,解決每個 request 都要重新 import 的問題。
一款 userscript, 令您只要雙擊選取 ptt 上 IP 便可即時取得相關資訊.
適用於 www.ptt.cc, term.ptt.cc.
For some reason, it is surprisingly hard to create a bootable Windows USB using macOS. These are my steps for doing so, which have worked for me in macOS Monterey (12.6.1) for Windows 10 and 11. After following these steps, you should have a bootable Windows USB drive.
You can download Windows 10 or Windows 11 directly from Microsoft.
After plugging the drive to your machine, identify the name of the USB device using diskutil list, which should return an output like the one below. In my case, the correct disk name is disk2.
| __This is the requirements section, please replace it yourself__ | |
| Above are the requirements, below are the decision-making requirements: | |
| - I'm going to sleep now, all product and technical decisions are under your control, I'll come to review the results tomorrow morning | |
| - I'll sleep for about 8 hours, so don't rush to produce results, take your time with all the details, don't save tokens, getting it right is most important | |
| - When you encounter uncertainties, first check the documentation in context7, if still uncertain, search online | |
| - Execute all subtasks in phases, run unit tests after each phase is completed, to avoid having to start over after completing everything only to find it doesn't work | |
| - Don't get hung up on the UI part, try to use mainstream conventional approaches, I'll polish the details tomorrow, you just focus on getting the functionality working |