| #!/bin/bash | |
| # idea|clion|datagrip etc. | |
| intellijproduct="idea" | |
| tarfile="" | |
| attempt=$(find . -iname "*$intellijproduct*.gz") | |
| uresp="" | |
| if [ "$attempt" != "" ]; then | |
| echo "" |
These instructions include running a local registry accessible from Kubernetes as well as from the
host development machine at registry.dev.svc.cluster.local:5000.
- Use the docker CLI to run the
registry:2container from Docker, listening on port5000, and persisting images in the~/.registry/storagedirectory.
This gist is out of date and I can no longer help much, as I got rid of my Mac.
Please visit T2 Linux website for more and better information:
This gist is just a compilation of the hard work that others have put in. I'm not a software developer, so if there are any mistakes or better ways of doing things, I'd appreciate any suggestions. Here's a list of the real heroes who made this possible:
| #!/bin/zsh | |
| # | |
| # Purpose: run specified command with specified arguments and cache result. If cache is fresh enough, don't run command again but return cached output. | |
| # Also cache exit status and stderr. | |
| # Copyright (c) 2019-2023 András Korn; License: GPLv3 | |
| # Use silly long variable names to avoid clashing with whatever the invoked program might use | |
| RUNCACHED_MAX_AGE=${RUNCACHED_MAX_AGE:-300} | |
| RUNCACHED_IGNORE_ENV=${RUNCACHED_IGNORE_ENV:-0} | |
| RUNCACHED_IGNORE_PWD=${RUNCACHED_IGNORE_PWD:-0} |
This guide provides instructions for an Arch Linux installation featuring full-disk encryption via LVM on LUKS and an encrypted boot partition (GRUB) for UEFI systems.
Following the main installation are further instructions to harden against Evil Maid attacks via UEFI Secure Boot custom key enrollment and self-signed kernel and bootloader.
You will find most of this information pulled from the Arch Wiki and other resources linked thereof.
Note: The system was installed on an NVMe SSD, substitute /dev/nvme0nX with /dev/sdX or your device as needed.
| package main | |
| import ( | |
| "bytes" | |
| "fmt" | |
| "io" | |
| "os" | |
| "strings" | |
| ) |
Uncle Bob, the well known author of Clean Code, is coming back to us with a new book called Clean Architecture which wants to take a larger view on how to create software.
Even if Clean Code is one of the major book around OOP and code design (mainly by presenting the SOLID principles), I was not totally impressed by the book.
Clean Architecture leaves me with the same feeling, even if it's pushing the development world to do better, has some good stories and present robust principles to build software.
The book is build around 34 chapters organised in chapters.
These rules are adopted from the AngularJS commit conventions.