The-Running-Dev

# Exampe .env file for the Doplarr docker-compose.yml

BotToken=INSERT_YOUR_KEY_HERE
ConfigRootPath=/path/to/your/discord-bot/data
RequestsAPIKey=INSERT_YOUR_KEY_HERE
RequestsDefaultID=1
RequestsHost=requests

The-Running-Dev

param (
    [switch] $verbose
)

# Function to log messages
function Log-Message {
    param (
        [string] $message,
        [string] $type = 'INFO'
    )

The-Running-Dev

# Resources
# Sample package: https://www.myqnap.org/product/radarr-qbase24/
# Create a simple package: https://cheng-yuan-hong.gitbook.io/qdk-qpkg-development-kit/creating-a-qpkg-package-using-qdk/creating-a-simple-qpkg-package
# QNAP SDK docs: https://edhongcy.gitbooks.io/qdk-qpkg-development-kit/content/

# You will need the QNAP SDK, https://github.com/qnap-dev/QDK
# Download the package and put it on your NAS
# SSH into the nas and go to the directory where the package is located

# Create the QNAP build evnironment

The-Running-Dev

using System;
using System.Runtime.InteropServices;

public class FxHook:IDisposable {

	const int nBytes = 5;

	IntPtr addr;
	Protection old;
	byte[] src = new byte[5];

The-Running-Dev

if ($env:TEAMCITY_VERSION) {
	# When PowerShell is started through TeamCity's Command Runner, the standard
	# output will be wrapped at column 80 (a default). This has a negative impact
	# on service messages, as TeamCity quite naturally fails parsing a wrapped
	# message. The solution is to set a new, much wider output width. It will
	# only be set if TEAMCITY_VERSION exists, i.e., if started by TeamCity.
	$host.UI.RawUI.BufferSize = New-Object System.Management.Automation.Host.Size(8192,50)
}

function TeamCity-Message([string]$text, [string]$status = 'NORMAL', [string]$errorDetails) {

The-Running-Dev

<#
Save to:  Create-Kavita-Structure.ps1
and run it with: .\Create-Kavita-Structure.ps1 -sourceDir 'DriveLetter:\PathToBooks' -kavitaDir 'DriveLetter:\PathToKavitaWatchedDir"
If sourceDir is not specified, assumes current directory (.)
If kavitaDir is not specified, assumes @Kavita under the current directory (.\@Kavita)

To test this without making any changes: Create-Kavita-Structure.ps1 -whatIf
#>
[CmdletBinding(SupportsShouldProcess = $true)]
Param(

The-Running-Dev

<#
.NOTES
How to use: Open Visual Studio, go to Tools – External Tools to bring up the External Tools dialog, add a new tools menu with the following configuration:
Title: Manage User Secrets (Or whatever you want)
Command: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe (Path to powershell.exe)
Arguments: Path-to-this-script(e.g. D:\VisualStudioTools\usersecrets.ps1)
Initial Directory: $(ProjectDir)

.PARAMETER ProjectFilePath
The csproj file's path, or keep it empty to search *.csproj file in initial directory

The-Running-Dev

/// <summary>
/// Checks if string is empty, null or white space
/// </summary>
/// <param name="value"></param>
/// <returns></returns>
public static bool IsEmpty(this string value)
{
  return string.IsNullOrEmpty(value) || string.IsNullOrWhiteSpace(value);
}

The-Running-Dev

# Set to preview version if the source branch is not the master branch
isPreviewVersion: ${{
  ne(variables['Build.SourceBranch'], 'refs/heads/master')
}}

The-Running-Dev

- task: AzureCLI@2
              name: generateToken
              displayName: Generating SAS Token
              inputs:
                azureSubscription: ${{variables.subscription}}
                scriptType: pscore
                scriptLocation: inlineScript
                inlineScript: |
                  $sasToken = az storage blob generate-sas `
                    --account-name ${{variables.templateStorageAccount}} `