| import { options } from "preact"; | |
| import { Signal } from "@preact/signals"; | |
| // Add `bind:value` to JSX types | |
| declare global { | |
| namespace preact.createElement.JSX { | |
| interface HTMLAttributes { | |
| "bind:value"?: Signal<string | string[] | number | undefined>; | |
| } | |
| } |
| #!/bin/bash | |
| ## Create the response FIFO | |
| rm -f response | |
| mkfifo response | |
| function handle_GET_home() { | |
| RESPONSE=$(cat home.html | \ | |
| sed "s/{{$COOKIE_NAME}}/$COOKIE_VALUE/") | |
| } |
Lines starting with # mean the commands have to be executed by root user under Linux shell (WSL distro).
All other commands have to be executed under Windows-PowerShell as Administrator.
New-VHD support.vhdx -SizeBytes 25GB -Dynamic -BlockSizeBytes 1MB
Write-Output "\\.\PhysicalDrive$((Mount-VHD -Path support.vhdx -PassThru | Get-Disk).Number)"I wasn't able to git fetch from Azure DevOps repos after upgrading openssh on my computer.
ssh -V
OpenSSH_8.8p1, OpenSSL 1.1.1l 24 Aug 2021
Turns out that OpenSSL has now turned off ssh-rsa by default:
This release disables RSA signatures using the SHA-1 hash algorithm by default.
But Azure DevOps doesn't support anything else... Add the following to your config file to re-enable ssh-rsa for Azure DevOps:
| FROM node:13-alpine as base | |
| LABEL maintainer="Isaak Eriksson <[email protected]>" | |
| ENV PUPPETEER_SKIP_CHROMIUM_DOWNLOAD true | |
| ENV PUPPETEER_EXECUTABLE_PATH /usr/bin/chromium-browser | |
| WORKDIR /src | |
| RUN apk update && apk add --no-cache --virtual \ |
| pragma solidity ^0.5.0; | |
| /** | |
| * @dev Wrappers over Solidity's arithmetic operations with added overflow | |
| * checks. | |
| * | |
| * Arithmetic operations in Solidity wrap on overflow. This can easily result | |
| * in bugs, because programmers usually assume that an overflow raises an | |
| * error, which is the standard behavior in high level programming languages. | |
| * `SafeMath` restores this intuition by reverting the transaction when an |
| let cachedMongoClient = null; | |
| let cachedMongoDb = null; | |
| exports.connect = async () => { | |
| if (cachedMongoDb && cachedMongoClient && cachedMongoClient.isConnected()) { | |
| return cachedMongoDb; | |
| } | |
| cachedMongoClient = await MongoClient.connect('MONGO_CONNECTION', { useNewUrlParser: true }); |
This set of instructions configures a fresh LEDE installation to run Homenet. They will likely work on a current build of OpenWrt.
There's lots of good info about Homenet elsewhere. See the External References section (below).
The general strategy is to connect your computer to the router's LAN Ethernet, convert the wireless and WAN interfaces to run Homenet, and test the changes so far. After things are working, configure the LAN Ethernet to Homenet through connect one of the (now Homenet) wireless interfaces.
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <style> | |
| body.loading #splash { | |
| opacity: 1; | |
| } | |
| #splash { | |
| position: absolute; | |
| top: 0; |
