This information source from the following url:
http://peter.sh/experiments/chromium-command-line-switches/
And also in the chromium source:
https://source.chromium.org/chromium/chromium/src/+/main:media/base/media_switches.cc
This information source from the following url:
http://peter.sh/experiments/chromium-command-line-switches/
And also in the chromium source:
https://source.chromium.org/chromium/chromium/src/+/main:media/base/media_switches.cc
An nginx configuration that can be added to your /etc/nginx/sites-enabled
directory to proxy from the local nginx server through to other servers running on other ports. Primarily this is useful when you want to view a site using HTTPS but don't want to associate the certificate with that local server.
The following proxys work:
http://localhost/ => http://localhost:9966/
https://localhost/ => http://localhost:9966/
https://localhost/<port>/ => http://localhost:<port>/
https://localhost// => http://localhost:/
Emoji guide:
When brightness controls stop responding manually trigger a brightness update. Once this is done brightness controls seem to respond again. Not sure if the lspci
command is required, when my linux foo is stronger I'm sure I'll know...
lspci -nn | grep VGA
echo 3500 | sudo tee /sys/class/backlight/intel_backlight/brightness
More generic instructions can be found here: https://github.com/umlaeute/v4l2loopback/wiki/Mplayer
git clone https://github.com/umlaeute/v4l2loopback
cd v4l2loopback
make
sudo make install
sudo modprobe v4l2loopback
Currently trawling NPM in search of a node module that makes working with CSS and browserified code "feel" better. My first thought was to seek out an existing project (or create one) that took a programmatic approach to CSS generation.
Here's what I've found:
server { | |
listen 443; | |
server_name localhost; | |
root html; | |
index index.html index.htm; | |
ssl on; | |
ssl_certificate server.crt; | |
ssl_certificate_key server.key; |
This is some research focused around looking for node modules that support the development of an application that makes heavy use of a central message bus for cross component communication. The process for identifying potential components was simply to start by looking for packages that depend node the node-redis module, as at this this stage we see redis being the mechanism for powering the bus.