Arc
defaults write company.thebrowser.Browser.plist ExtensionManifestV2Availability -int 2
Chrome
defaults write com.google.Chrome.plist ExtensionManifestV2Availability -int 2
Chrome Beta
Arc
defaults write company.thebrowser.Browser.plist ExtensionManifestV2Availability -int 2
Chrome
defaults write com.google.Chrome.plist ExtensionManifestV2Availability -int 2
Chrome Beta
#!/usr/bin/env bash | |
## --------------- | |
## Setup | |
## --------------- | |
CURRENT_BASH=$(ps -p $$ | tail -n 1 | awk '{ print $4 }' | perl -pe 's#.*[-/](\w)#$1#'); | |
case "${CURRENT_BASH}" in | |
zsh) | |
CURRENT_DIR=$(cd "$(dirname "${0}")" && pwd); | |
;; |
<?php | |
namespace Tests\Integration; | |
use Symfony\Bundle\FrameworkBundle\Test\KernelTestCase; | |
use Symfony\Component\HttpFoundation\Request; | |
use Symfony\Component\HttpKernel\Controller\ControllerResolverInterface; | |
use Symfony\Component\HttpKernel\HttpKernelInterface; | |
use Symfony\Component\Routing\RouterInterface; |
The following steps will describe how to build PHP from source including PHP's Apache module as it is no longer part of macOS starting with macOS Monterey.
If this is for a development environment, you can simply install PHP with Homebrew using the command brew install php
. This guide is for cases where you need a more portable PHP without heavily dependening on external libraries.
This page will help you run continuous integration for PHP CodeSniffer and PHP-CS-Fixer using GitHub Actions.
To setup GitHub Actions in your repository, create a .github/workflows/ci.yml
file in your repository and commit it.
The content of that file depends on the tool you want to run, please read the examples below.
Note: the examples below are provided to get you started easily, it is possible you may need to adjust them to fit your project.
brew install [email protected]
If you need to have [email protected] first in your PATH run:
echo 'export PATH="/usr/local/opt/[email protected]/bin:$PATH"' >> ~/.zshrc
# Unofficial Hombrew Cask for Audacity 2.3.2 (recent 64-bit version) | |
# Made entirely for fun and to demonstrate how to get around fosshub's limitations. | |
# Problem: Audacity's binary is hosted on fosshub and they don't provide a fixed url! The seems to intentionally try to prevent "hot-linking". | |
# Solution: Make a request to fosshub's special XHR endpoint to get the signed download url. Then just pass that URL to Homebrew | |
require 'net/http' | |
require 'json' | |
require 'uri' |
⚠️ Note 2023-01-21
Some things have changed since I originally wrote this in 2016. I have updated a few minor details, and the advice is still broadly the same, but there are some new Cloudflare features you can (and should) take advantage of. In particular, pay attention to Trevor Stevens' comment here from 22 January 2022, and Matt Stenson's useful caching advice. In addition, Backblaze, with whom Cloudflare are a Bandwidth Alliance partner, have published their own guide detailing how to use Cloudflare's Web Workers to cache content from B2 private buckets. That is worth reading,
The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the
last update: Dec 4, 2020