manics

channels:
  - conda-forge
dependencies:
  - notebook>=7
  - jupyter-offlinenotebook

manics

name: jupyter
channels:
  - conda-forge/label/jupyterlab_beta
  - conda-forge
dependencies:
  - jupyterlab
  - jupyter-server-proxy
  - marimo

manics

#!/bin/sh
set -eux

sh -c 'sleep 1h && /bin/echo a97bfa0b-025f-4750-aeaf-5d27c7337057 cryptnono.banned.string1'
exit 1

manics

#!/bin/bash

loopdevice=/dev/loop0
loopfile=crypt.loop

#megabytes
loopsize=256

#/dev/mapper/xxxxx when open
cryptmapper=myCrypt

manics

# Access a Kubernetes node root filesystem under /mnt/root
# Replace nodename.k8s.example.org with the Kubernetes node you want to access
#
#   kubectl apply -f root-host-volume-shell.yaml 
#   kubectl exec -it root-host-volume-shell -- bash
---
apiVersion: v1
kind: Pod
metadata:
  name: root-host-volume-shell

manics

repos:
  - repo: https://github.com/pycqa/isort
    rev: 5.12.0
    hooks:
      - id: isort

  - repo: https://github.com/psf/black
    rev: 23.3.0
    hooks:
      - id: black

manics

#!/bin/sh

# Based on Windows EC2Launch Module/Scripts/Send-AdminCredentials.ps1 script
#
# Include this at the end of your EC2 userdata
# Once the console output is available you should be able to run
# aws ec2 get-password-data --instance-id=INSTANCE_ID --priv-launch-key SSH_PRIVATE_PEM_FILE
# to get the randomly generated password
#
# Note that SSH password authentication is disabled on the SSH server by default

manics

# make sure crypt module in use
sudo modprobe dm-crypt

# Find out which drive it was with the following command:
sudo fdisk -l

# You must mount /dev/sda3 myvolume
# use cryptsetup, device is accessible under /dev/mapper/myvolume
sudo cryptsetup luksOpen /dev/sde3 myvolume

manics

apiVersion: v1
kind: Pod
metadata:
  labels:
    app: netshoot
  name: netshoot
spec:
  containers:
    - args:
        - sleep

manics

#!/bin/sh
set -eux
date
false