These learning resources primarily focus on programming using Good Design Principles and Design Patterns
- There is an emphasis on learning using PHP, although most patterns are universal to every object orientated language.
local function getOptimizeLevel() | |
local function dupclosure() | |
return function() end | |
end | |
local O0 = dupclosure() ~= dupclosure() | |
local function inlinefunction() | |
return debug.info(1, "f") | |
end |
# 6 band sink equalizer | |
# | |
# Copy this file into a conf.d/ directory such as | |
# ~/.config/pipewire/filter-chain.conf.d/ | |
# | |
context.modules = [ | |
{ name = libpipewire-module-filter-chain | |
args = { | |
node.description = "Internal Speakers Equalizer Sink" | |
media.name = "Internal Speakers Equalizer Sink" |
### START - Update this section with relevant details ### | |
substitutions: | |
device_name: "device-name-here" | |
friendly_name: Device Name Here | |
board_type: esp32dev | |
framework: esp-idf # arduino or esp-idf (recommended for ESP32) | |
# ESPHome API used by Home Assistant, etc |
I tried the WSL and it isn't quite seamless enough for me. I ran in to problems when editing in VSCode and having watchers on my files (ng serve
, dotnet watch run
, etc.). In addition, I kept running in to problems that only manifest themselves when running in WSL. For example, this issue with doing production builds and the terser plugin has made many a developer rage-quit on using WSL. Just figuring out that it was an issue with the WSL took a lot of time.
That terser plugin issue was never resolved and I ended up having to keep a git bash window open in addition to my WSL console window so I could do production builds. To make matters worse, my npm packages were platform-dependent so I couldn't use the same project folder. So, my procedure was: commit whatever changes to test branch, push to repo, git pull
on my "windows" project folder, and do a production build there
Microsoft.HEVCVideoExtension
) app by entering the following store URL.
https://www.microsoft.com/en-us/p/hevc-video-extensions-from-device-manufacturer/9n4wgh0z6vhq
There are many companies providing sales tax API. Out of all the companies, Avalara offers free API service for sales Tax. This gist is all about setting up avalara API and querying it.
The Free-To-Use API by avalara has some restrictions. Usage of this API is subject to rate limits. Users who exceed the rate limit will receive HTTP response code 429 - Too Many Requests
. The requirement for this API is to create an avalara free trail account. You can create a free account using this link create free account.
Once you have filled the form from above link, you will get an e-mail containing temporary credentials to login the avalara account. The e-mail will look something like this:
pages: | |
image: node:latest | |
stage: deploy | |
script: | |
- npm install -g redoc-cli | |
# public/index.html is the output | |
# documentation/openapi.yaml is the input | |
- redoc-cli bundle -o public/index.html documentation/openapi.yaml | |
artifacts: | |
paths: |
The game is not installed or downloaded via Epic, instead the Epic Games Launcher launches Origin to link your account to install the game. This can be done manually to still be able to install and download the game without the Epic Games Launcher.
Origin needs to be installed and working for this, please consult https://github.com/lutris/docs/blob/master/Origin.md for how to get it running on Linux via Lutris.
On Windows Origin just needs to be installed and ideally updated to the current version.