E. Lofgren (TiER1) ejlofgren

Upgrade the Repositories

sudo apt update sudo apt upgrade

Install MySQL 5.7

sudo apt install mysql-server

Secure MySQL Installation

sudo apt install mysql-server #To do the high security provide all answers to yes

Windows 10 version 2004 - Installing Node.js on Windows Subsystem for Linux (WSL/WSL2)

UPDATE (Fall 2020): This gist is an updated version to the Windows 10 Fall Creators Update - Installing Node.js on Windows Subsystem for Linux (WSL) guide, I usually just keep here notes, configuration or short guides for personal use, it was nice to know it also helps other ppl, I hope this one too.

Windows updated windows subsystem for linux to version 2, as the F.A.Q stated you can still use WSL version 1 side by side with version 2. I'm not sure about existing WSL machines surviving the upgrade process, but as always backup and 🤞. NOTE: WSL version 1 is not replace/deprecated, and there ar

$ wget -e robots=off -r -np 'http://example.com/folder/'

-e robots=off causes it to ignore robots.txt for that domain
-r makes it recursive
-np = no parents, so it doesn't follow links up to the parent folder

PM2 as a Windows Service under Local Service

Written for jon-hall/pm2-windows-service#3

This is a PoC for running PM2 as a Windows Service under the Local Service account instead of the Local System account.

Prerequsites

Neither pm2 or pm2-windows-service installed yet. (The Powershell script will run npm i)
- At the very least, you should run pm2-service-uninstall before running this script
npm and npm-cache global folders should be somewhere accessible to NT AUTHORITY\LocalService.
- Instructions for moving them to C:\ProgramData\

	"scripts": {
	"serve": "vue-cli-service serve",
	"build:admin": "rimraf vue.config.js && copy vue.configAdmin.js vue.config.js && vue-cli-service build --dest dist/admin src/admin/main.js && rimraf vue.config.js && copy vue.configDefault.js vue.config.js",
	"build:client": "rimraf vue.config.js && copy vue.configClient.js vue.config.js && vue-cli-service build --dest dist/client src/client/main.js && rimraf vue.config.js && copy vue.configDefault.js vue.config.js",
	"lint": "vue-cli-service lint"
	},

	<!DOCTYPE html>
	<html>
	<head>
	<meta charset="utf-8">
	<title>Shape selection</title>
	<!-- Vue for doing stuff-->
	<script src="https://unpkg.com/vue/dist/vue.js"></script>
	<!-- Paper for handling graphics -->
	<script src="https://unpkg.com/[email protected]/dist/paper-full.min.js"></script>
	<!-- Axios for making API calls -->

	'use strict';

	var url = require('url');
	var target = 'http://www.yourwebsite.com'; // Change this one

	exports.handler = function(event, context, callback) {
	var urlObject = url.parse(target);
	var mod = require(
	urlObject.protocol.substring(0, urlObject.protocol.length - 1)
	);

	namespace Analogy
	{
	/// <summary>
	/// This example shows that a library that needs access to target .NET Standard 1.3
	/// can only access APIs available in that .NET Standard. Even though similar the APIs exist on .NET
	/// Framework 4.5, it implements a version of .NET Standard that isn't compatible with the library.
	/// </summary>INetCoreApp10
	class Example1
	{
	public void Net45Application(INetFramework45 platform)

	$serverName = ".\SQLExpress"
	$backupDirectory = "D:\backupSQL"
	$daysToStoreDailyBackups = 7
	$daysToStoreWeeklyBackups = 28
	$monthsToStoreMonthlyBackups = 3

	[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SqlServer.SMO") \| Out-Null
	[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SqlServer.SmoExtended") \| Out-Null
	[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SqlServer.ConnectionInfo") \| Out-Null
	[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SqlServer.SmoEnum") \| Out-Null

	using System;
	using System.Collections.Specialized;
	using System.IO;
	using System.Net;
	using System.Text;
	using Authy.Net;
	using Newtonsoft.Json;

	namespace Authy.Net
	{