Christopher M Pieper xntric78

Docker host:

Install Jupyterhub and Jupyterlab The Hard Way

The combination of Jupyterhub and Jupyterlab is a great way to make shared computing resources available to group.

These instruction are a guide for a manual, 'bare metal' install of Jupyterhub and Jupyterlab. This is ideal for running on a single server: build a beast of a machine and share it within your lab, or use a virtual machine from any VPS or cloud provider.

This guide has similar goals to that of The Littlest Jupyerhub setup

	<!-- : Begin batch script
	@setlocal DisableDelayedExpansion
	@set uivr=v45
	@echo off
	:: ### Configuration Options ###

	:: change to 1 to enable debug mode (can be used with unattended options)
	set _Debug=0

	:: change to 0 to turn OFF Windows or Office activation processing via the script

	import aws_assume_role_lib # https://github.com/benkehoe/aws-assume-role-lib

	account_role_name = "YOUR_ACCOUNT_ROLE_NAME_HERE" # TODO: put your role name here

	management_account_session = boto3.Session()
	# if you're using AWS SSO in your management account and there's a specific role for this work, you could use aws-sso-lib
	# https://github.com/benkehoe/aws-sso-util/blob/master/lib/README.md
	# management_account_session = aws_sso_lib.get_boto3_session(start_url, sso_region, management_account_id, management_role_name, region=sso_region)

	orgs = management_account_session.client('organizations')

	terraform {
	required_providers {
	aws = {
	source = "hashicorp/aws"
	version = "3.19.0"
	}
	}
	}

	provider "aws" {

	import json
	from os import getenv, path
	from string import Template
	from subprocess import run
	from sys import exit


	ZONE_ID = getenv("ZONE_ID")
	ZONE_FILE = getenv("ZONE_FILE")
	TERRAFORM_DIR = getenv("TERRAFORM_DIR")

	function aws-sso-access-token() {
	find "$HOME/.aws/sso/cache" -type f ! -name 'botocore*' -exec jq -r '.accessToken' {} \; \| head -n1
	}

	function aws-sso-list-accounts() {
	aws sso list-accounts --access-token "$(aws-sso-access-token)" "$@"
	}

	function aws-sso-list-account-roles() {
	aws sso list-account-roles --access-token "$(aws-sso-access-token)" "$@"

	@echo off
	title Activate Windows 11 (ALL versions) for FREE - MSGuides.com&cls&echo =====================================================================================&echo #Project: Activating Microsoft software products for FREE without additional software&echo =====================================================================================&echo.&echo #Supported products:&echo - Windows 11 Home&echo - Windows 11 Professional&echo - Windows 11 Education&echo - Windows 11 Enterprise&echo.&echo.&echo ============================================================================&echo Activating your Windows...&cscript //nologo slmgr.vbs /ckms >nul&cscript //nologo slmgr.vbs /upk >nul&cscript //nologo slmgr.vbs /cpky >nul&set i=1&wmic os \| findstr /I "enterprise" >nul
	if %errorlevel% EQU 0 (cscript //nologo slmgr.vbs /ipk NPPR9-FWDCX-D2C8J-H872K-2YT43 >nul\|\|cscript //nologo slmgr.vbs /ipk DPH2V-TTNVB-4X9Q3-TJR4H-KHJW4 >nul\|\|cscript //nologo slmgr.vbs /ipk YYVX9-NTFWV-6MDM3-9PT4T-4M68B >nul\|\|cscript //nologo

	#!/bin/sh

	SERVICE_FILE=nextdns-catchall.service
	SOURCE_FILE_PATH=/data/${SERVICE_FILE}
	SYSTEMD_FILE_PATH=/etc/systemd/system/${SERVICE_FILE}
	if [ ! -f $SOURCE_FILE_PATH ];
	then
	echo "Can't find service file"
	exit 1
	fi

	$SQLSvcMSA = 'DOMAIN\MSASQLName$'
	$AgtSvcMSA = 'DOMAIN\MSAAgentName$'

	# These are required but not used since we are using MSAs
	$SQLSvcAccount = New-Object System.Management.Automation.PSCredential($SQLSvcMSA, $('mypassword' \| ConvertTo-SecureString -asPlainText -Force))
	$AgtSvcAccount = New-Object System.Management.Automation.PSCredential($AgtSvcMSA, $('mypassword' \| ConvertTo-SecureString -asPlainText -Force))


	Configuration ServerBuild {
	Import-DscResource -ModuleName 'PSDscResources'