- New York, NY
-
23:11
(UTC -04:00)
Highlights
- Pro
Lists (2)
Sort Name ascending (A-Z)
- All languages
- ASL
- Assembly
- Batchfile
- C
- C#
- C++
- CMake
- CSS
- CUE
- Clojure
- Dart
- Dockerfile
- Elixir
- Elm
- Emacs Lisp
- Erlang
- FreeMarker
- Go
- Go Template
- Groovy
- HCL
- HLSL
- HTML
- Handlebars
- Haskell
- Java
- JavaScript
- Jinja
- Jsonnet
- Jupyter Notebook
- Just
- LLVM
- Less
- Limbo
- Lua
- MDX
- Makefile
- Markdown
- Meson
- Mustache
- Nim
- Nix
- Nu
- Nushell
- Objective-C
- Open Policy Agent
- OpenSCAD
- PHP
- PLpgSQL
- Perl
- Pkl
- PowerShell
- Pug
- Puppet
- Python
- QML
- RPM Spec
- Rascal
- Roff
- RouterOS Script
- Ruby
- Rust
- SCSS
- SaltStack
- Scala
- Shell
- Slim
- Smarty
- Solidity
- Starlark
- Swift
- TypeScript
- Vala
- Vim Script
- Vue
- YAML
- Zig
- reStructuredText
Starred repositories
GTFOBins is a curated list of Unix-like executables that can be used to bypass local security restrictions in misconfigured systems.
Wife approved HomeOps driven by Kubernetes and GitOps using Flux
A template for deploying a Talos Kubernetes cluster including Flux for GitOps
My home or for-home infrastructure written as code, adhering to GitOps practices. Mirror of https://git.bjw-s.dev/bjw-s/home-ops
GitOps principles to define kubernetes cluster state via code
A collection of roles to manage Ansible Automation Platform 2.5+ with code
An Ansible playbook that applies the principle of the Infrastructure as Code on a QEMU/KVM environment.
☸️ A collection of Helm charts, based on the bjw-s common library chart.
A mono repository for my home infra and Kubernetes cluster adhering to Infrastructure as Code (IaC) and GitOps practices
💾 A collection of my personal ESPHome configs and packages.
Automated Arch Linux configuration with Ansible (deprecated, I switched to NixOS)
Kubernetes cluster managed by Flux and using git as a "single source of truth."