| name: gmft | |
| channels: | |
| - conda-forge | |
| dependencies: | |
| - pytorch | |
| - pip | |
| - pip: | |
| - gmft | |
| #!/bin/sh | |
| # First run postgres, e.g. | |
| # nerdctl run -it --rm -p5432:5432 -e POSTGRES_PASSWORD=password docker.io/library/postgres:17 | |
| set -eu | |
| # Postgres connection details | |
| PG_HOST=127.0.0.1 | |
| PG_USER=postgres | |
| PG_SCHEMA=public |
This gist is a quick explainer on how to install and configure gVisor on K3s. There is a sort of hidden gotcha if you aren't reading the documentation thoroughly. If you already have a K3s cluster setup skip to the appropriate section below.
Install K3s as described in the documentation.
Includes sample notebooks from https://github.com/dotnet/interactive/tree/main/samples
| name: deno | |
| channels: | |
| - conda-forge | |
| dependencies: | |
| - dotnet>=8 |
| name: deno | |
| channels: | |
| - conda-forge | |
| dependencies: | |
| - deno>=2 |
It's often difficult to find the correct configuration for JupyterHub Authenticators, especially LDAP.
This command line utility loads your jupyterhub_config.py file, and attempts to login using a configured username and password with debug logging enabled.
This should allow you to quickly see whether your Authenticator configuration is correct.
| # Example of using JupyterHub with an Apache proxy under a prefix | |
| version: "3" | |
| services: | |
| jhub: | |
| image: quay.io/jupyterhub/jupyterhub-demo:5.1.0 | |
| networks: | |
| - jhub | |
| volumes: |
| name: nbgitpuller | |
| channels: | |
| - conda-forge | |
| dependencies: | |
| - python=3.12 | |
| - nbgitpuller |
