crystal wasm.cr
php -S localhost:3000
- open your browser
- open dev tool js console
crystal.add(1, 2)
Registering Rancher managed clusters in Argo CD doesn't work out of the box unless the Authorized Cluster Endpoint is used. Many users will prefer an integration of Argo CD via the central Rancher authentication proxy (which shares the network endpoint of the Rancher API/GUI). So let's find out why registering clusters via Rancher auth proxy fails and how to make it work.
Hint: If you are just looking for the solution scroll to the bottom of this page.
How to Force RGB Color Output instead of YPbPr on your M1 Apple Silicon Mac for an External Monitor.
This step-by-step video tutorial will guide you through the procedure of forcing RGB color output on your M1 Mac.
Here is the direct link to the video tutorial: https://www.youtube.com/watch?v=Z1EqH3fd0V4
The video also has Closed Captions (Subtitles) that you can enable, to make it easier to follow if needed.
I recommend running Dmitry’s latest resonance testing branch and using the pulses method outlined below:
https://github.com/Klipper3d/klipper/issues/4560
https://github.com/dmbutyugin/klipper/tree/resonance-test-methods
I would only go down this path if you're getting ghosting with really high speed prints. On the Annex Engineering K3 for example, no matter how perfect the graphs looked, I was still getting some ghosting. That prompted me to go down this path. I'm now able to print at 20-30k acceleration, 250-350mm/s, and 15scv with perfect quality that can usually only be seen at significantly slower speeds.
The default settings in Klipper have the damping ratio set to .1. This should be fine for most people with sane settings. I like to go for the insane.
Our goal today is to configure a VLAN for "Internet of Things" devices that is sequestered from our default private network. Devices on the private network are free to initiate connections into our IoT VLAN, but devices in the IoT VLAN should not be able to initiate connections to one another or to the private network.
The focus of this document is the configuration of UniFi system to allow Sonos speakers to operate across VLANs. Creating the VLAN itself is left to the user (there are many other guides out there that cover this topic). For our discussion, here are the networks we'll be working with:
10.1.1.0/24
- this is our Private network where our trusted devices live.10.1.20.0/24
- this is our IoT network configured as VLAN 20; Sonos devices live here.
Each Sonos speaker is assigned a static IP address via a DHCP reservation. These static IP addresses enable us to write some targeted firewall to allow the Sonos software to work across our V
;; Logseq Default Query 6-pack | |
;; --------------------------- | |
;; | |
;; Pontus Sundén (@psu) | |
;; October 28, 2022 | |
;; | |
;; Attribution | |
;; - https://gist.github.com/sawhney17/3a1b04936f35df80253431a61cb74737 | |
;; | |
;; --------------------------- |