Last Revised: 2024-09-07
I made this guide to help anyone interested in editing the Windows Registry.
It is possible to modify the entries of the Windows Registry.
To do this, you need to create a file that ends with the extension .reg.
#!/bin/bash | |
# Polls AT&T's DHCP server for updates, to keep static IPs alive. | |
# This allows UDM Pro users to set their DHCP IP as 'static' in the 'Internet' section | |
# allowing the use of static IP configuration in Unifi Network. | |
# 1. Find your DHCP IP. | |
# 2. Set Internet IPv4 to Static IP, and enter your DHCP address. Gateway is going to be .1 | |
# 3. Add your static IP block to Additional IP Addresses | |
# 4. Place this script in the on_boot.d/ directory: https://github.com/unifi-utilities/unifios-utilities/tree/main/on-boot-script | |
# 5. After reboot, check the script is working: cat /var/log/udhcpc.log |
Decompiled DLL with ILSpy to identify various commands.
Most commands can be found in DDM2._0_UX.CmdBackground.cmdService_DoWork
Write commands can be prefixed with int:command to specify which monitor to send the command to.
.\DDM.exe /0:writebrightnesslevel 50
See also:
Service | Type | Storage | Limitations |
---|---|---|---|
Amazon DynamoDB | 25 GB | ||
Amazon RDS | |||
Azure SQL Database | MS SQL Server | ||
👉 Clever Cloud | PostgreSQL, MySQL, MongoDB, Redis | 256 MB (PostgreSQL) | Max 5 connections (PostgreSQL) |
Table of Contents
If you're looking for a way to activate Windows 10 or 11 for free, the command line is one of the most effective methods. This approach allows you to activate your operating system using your product key and doesn't require any third-party programs. In this article, we'll walk you through the process.
Using the command line for activating Windows allows you to:
<a href="https://www.buymeacoffee.com/gbraad" target="_blank"><img src="https://www.buymeacoffee.com/assets/img/custom_images/orange_img.png" alt="Buy Me A Coffee" style="height: 41px !important;width: 174px !important;box-shadow: 0px 3px 2px 0px rgba(190, 190, 190, 0.5) !important;-webkit-box-shadow: 0px 3px 2px 0px rgba(190, 190, 190, 0.5) !important;" ></a>
This logging setup configures Structlog to output pretty logs in development, and JSON log lines in production.
Then, you can use Structlog loggers or standard logging
loggers, and they both will be processed by the Structlog pipeline (see the hello()
endpoint for reference). That way any log generated by your dependencies will also be processed and enriched, even if they know nothing about Structlog!
Requests are assigned a correlation ID with the asgi-correlation-id
middleware (either captured from incoming request or generated on the fly).
All logs are linked to the correlation ID, and to the Datadog trace/span if instrumented.
This data "global to the request" is stored in context vars, and automatically added to all logs produced during the request thanks to Structlog.
You can add to these "global local variables" at any point in an endpoint with `structlog.contextvars.bind_contextvars(custom
require 'socket' | |
require 'rack' | |
require 'rack/lobster' | |
app = Rack::Lobster.new | |
server = TCPServer.new 5678 | |
while session = server.accept | |
request = session.gets | |
puts request |