| function makemp4 { | |
| # List of supported video file extensions, including 3G2 | |
| $extensions = @("*.mkv", "*.avi", "*.mov", "*.3g2") # Add other extensions as needed | |
| # Display the supported formats at the start of the script. | |
| $formats = $extensions -replace "\*\.", "" -join ", " | |
| Write-Host "Supported formats: $formats" | |
| # Get all video files in the current directory that match the supported extensions. | |
| $videoFiles = Get-ChildItem .\* -Include $extensions |
| function Command-Exists { | |
| param($command) | |
| $oldPreference = $ErrorActionPreference | |
| $ErrorActionPreference = 'SilentlyContinue' | |
| $exists = Get-Command $command -ErrorAction SilentlyContinue | |
| $ErrorActionPreference = $oldPreference | |
| return $exists -ne $null | |
| } | |
| function Check-ImageMagick { |
| ## Open sln in Visual Studio from the containing folder | |
| function Start-VisualStudio([string]$folder) | |
| { | |
| # Set folder to current directory if not specified | |
| if ([string]::IsNullOrWhiteSpace($folder)) | |
| { | |
| $folder = $(Get-Location).Path | |
| } | |
| # Ensure folder path ends with a backslash |
| <# | |
| .SYNOPSIS | |
| Converts video files of various formats (e.g., MKV, AVI, MOV) to MP4 using FFmpeg. | |
| .DESCRIPTION | |
| This script searches the current directory for video files with specified extensions | |
| and converts them to MP4 format without re-encoding (using stream copy). | |
| The script uses FFmpeg for conversion and suppresses detailed output during the process. | |
| Any errors encountered during the conversion are logged. |
This is for a single SD card. You can use two SD cards, but I find a single SD card is cheap and easy to manage.
Download RG35XX-MicroSDCardImage.7z.001 and RG35XX-MicroSDCardImage.7z.002
Extract RG35XX-MicroSDCardImage.7z.001 using 7-zip (open the .7z.001 file) to somewhere on your hard drive (not the USB card!).
| # https://mattou07.net/posts/create-a-self-signed-certificate-for-iis-with-powershell/ | |
| # https://www.yaplex.com/how-to-create-a-self-signed-certificate-for-iis-using-powershell/ | |
| # https://adamtheautomator.com/new-selfsignedcertificate/ | |
| $binding = Read-Host -Prompt 'Enter the site you need a cert for: ' | |
| $cert = New-SelfSignedCertificate -DnsName "$binding" -NotAfter (Get-Date).AddMonths(72) -CertStoreLocation "cert:\LocalMachine\My" | |
| Write-Host "Cert [$binding] has been created in the local machine cert store." | |
| Write-Host "Cert will expire in 6 years." |
| DECLARE @SearchStr nvarchar(100) = 'SEARCH_TEXT' | |
| DECLARE @Results TABLE (ColumnName nvarchar(370), ColumnValue nvarchar(3630)) | |
| SET NOCOUNT ON | |
| DECLARE @TableName nvarchar(256), @ColumnName nvarchar(128), @SearchStr2 nvarchar(110) | |
| SET @TableName = '' | |
| SET @SearchStr2 = QUOTENAME('%' + @SearchStr + '%','''') | |
| WHILE @TableName IS NOT NULL |
nodejs has some oddities when used on windows, below are some notes to address them.
Message "npm WARN config global '--global','--local' are deprecated. Use '--location=global' instead"
Referencing this stackoverflow thread: https://stackoverflow.com/questions/72401421/message-npm-warn-config-global-global-local-are-deprecated-use-loc
As of July 2022:
| #GenerateSelfSignedCert_2022.ps1 | |
| # Information from: https://www.tutorialspoint.com/how-to-create-a-self-signed-certificate-using-powershell | |
| # Additional/Similar information from: https://petri.com/create-self-signed-certificate-using-powershell | |
| # Get Current Directory | |
| $curDir = Get-Location | |
| #Write Header | |
| Write-Host "`n WARNING: This script is provided AS-IS with no warranties and confers no rights." -ForegroundColor Yellow |
We are increasingly using, or being required to use, SSL-encrypted sessions (or technically, TLS-encrypted sessions) for application services. In technical terms, because the Fully Qualified Domain Name (FQDN) in the Uniform Resource Locator (URL) used by a client to access a service needs to match the Common Name (CN) in the certificate used by that service, we potentially have a proliferation of certificates (at least one per server) that need to be available to clients
One approach to addressing this proliferation is to use wildcard certificates that match multiple FQDNs within a domain. Below is a discussion on generating self-signed wildcard certificates as a way of addressing this
What