| session=lxqt | |
| geometry=1920x1080 | |
| localhost # comment this out to allow connections from anywhere | |
| alwaysshared |
| #!/usr/bin/env zsh | |
| # WARNING: THIS SCRIPT WILL AGGRESSIVELY DESTROY ALL DATA ON ALL DRIVES | |
| # ON THIS SYSTEM!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
| # | |
| # This script assumes 3 drives (sda sdb and sdc) are present and the | |
| # first 2 are identical in size. The majority of the operating system | |
| # is installed onto a mirror of sda and sdb. Home is installed on sdc. | |
| ######################################################################## | |
| declare adm_user='o0-o' |
This is a collection of free e-books about Artificial Intelligence(Machine Learning, Planning) and Data Science etc. .
ML, ebook, ebooks, books, book, machine learning, statistics, free
Machine Learning Systems - Principles and Practices of Engineering Artificially Intelligent Systems
| #region Ensure the WinRm service is running | |
| Set-Service -Name "WinRM" -StartupType Automatic | |
| Start-Service -Name "WinRM" | |
| #endregion | |
| #region Enable PS remoting | |
| if (-not (Get-PSSessionConfiguration) -or (-not (Get-ChildItem WSMan:\localhost\Listener))) { | |
| Enable-PSRemoting -SkipNetworkProfileCheck -Force | |
| } | |
| #endregion |
| #cloud-config | |
| package_update: true | |
| manage_resolv_conf: true | |
| resolv_conf: | |
| nameservers: | |
| - '8.8.8.8' | |
| - '8.8.4.4' | |
| - '1.1.1.1' |
This document shows how to deploy an OpenShift instance on a server using CodeReady Containers (crc) that can be accessed remotely from one or more client machines (sometimes called a "headless" instance). This provides a low-cost test and development platform that can be shared by developers. Deploying this way also allows a user to create an instance that uses more cpu and memory resources than may be available on his or her laptop.
While there are benefits to this type of deployment, please note that the primary use case for crc is to deploy a local OpenShift instance on a workstation or laptop and access it directly from the same machine. The headless setup is configured completely outside of crc itself, and supporting a headless setup is beyond the mission of the crc development team. Please do not ask for changes to crc to support this type of deployment, it will only cost the team time as they politely decline :)
The instructions here were tested with F
| import ec2 = require('@aws-cdk/aws-ec2'); | |
| import cdk = require('@aws-cdk/core'); | |
| import { Fn, Tag, Resource } from '@aws-cdk/core'; | |
| import { AmazonLinuxImage, UserData, InstanceType } from '@aws-cdk/aws-ec2'; | |
| import { Role, ServicePrincipal, ManagedPolicy, CfnInstanceProfile } from '@aws-cdk/aws-iam' | |
| /** | |
| * Create my own Ec2 resource and Ec2 props as these are not yet defined in CDK | |
| * These classes abstract low level details from CloudFormation |
See also:
vinegar.vim, which makes - open netrw in the directory of the current file, with the cursor on the current file (and pressing - again goes up a directory). Vinegar also hides a bunch of junk that's normally at the top of netrw windows, changes the default order of files, and hides files that match wildignore.
With vinegar, . in netrw opens Vim's command line with the path to the file under the cursor at the end of the command. ! does the same but also prepends ! at the start of the command. y. copies the absolute path of the file under the cursor. ~ goes to your home dir. Ctrl+6 goes back to the file (buffer) that you had open before you opened netrw.
To launch netrw:
| $schema: 'https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#' | |
| contentVersion: 1.0.0.0 | |
| parameters: | |
| logicAppName1: | |
| type: string | |
| metadata: | |
| description: Name of the Logic App. | |
| logicAppName2: | |
| type: string | |
| metadata: |
| # Bash best practices and style-guide | |
| Just simple methods to keep the code clean. | |
| Inspired by [progrium/bashstyle](https://github.com/progrium/bashstyle) and [Kfir Lavi post](http://www.kfirlavi.com/blog/2012/11/14/defensive-bash-programming/). | |
| ## Quick big rules | |
| * All code goes in a function | |
| * Always double quote variables |
