Explore >> Select a destination
|
You are here 
|
techtldr.com | ||
| | | | |
emmanuelbernard.com
|
|
| | | | | tl;dr; using powerline and having it fail after a homebrew update? Read on. If you have tuned a bit your terminal in macOS, you might be using Powerline. It prettities your command line enough to warrant some trouble installing it. And it does it to vim status lines too. Now if you also use homebrew, every so often you see something like this when starting a new terminal window -bash: /usr/local/bin/powerline-daemon: /usr/local/opt/python/bin/python3.6: bad interpreter: No such file or directory I always fiddle with things until I get it fixed again. So here it is reported for posterity. The Python interpreter has been updated behind your back and the installed modules end up referencing the old interpreter. For powerline, here are the steps pip uninstall -y powerline-status brew update && brew upgrade python pip install powerline-status Note that I use Python 2 and not Python 3. From what I remember, I had troubles making it run properly on v3. Here is a more generic solution, courtesy of bnaecker at StackOverflow. pip list | cut -d " " -f 1 > package-list.txt # Store package names without versions pip uninstall -y $(cat package-list.txt) # Cannot use redirection brew update && brew upgrade python pip install $(cat package-list.txt) Back to work. | |
| | | | |
dusty.phillips.codes
|
|
| | | | | UPDATE: I've updated the Inko Formula on Homebrew to 0.11.0, so you may just want to use brew install inko instead. That said, There are a few bugfixes on Inko that didn't make it to the 0.11.0 release, so you may want to build off the main branch instead. I have a blog article in progress about why I'm super excited about the Inko Programming Language. It's nowhere near completion, however, and I wanted to share how I got the latest version Inko running on MacOS (Ventura). | |
| | | | |
soffes.blog
|
|
| | | | | Today, my new 13-inch MacBook Pro arrived! I was super excited to get it out of the box and set it up. This thing is fast! I am already very... | |
| | | | |
blogops.mixinet.net
|
|
| | | After my previous posts related to Argo CD (one about argocd-autopilot and another with some usage examples) I started to look into Kluctl (I also plan to review Flux, but I'm more interested on the kluctl approach right now). While reading an entry on the project blog about Cluster API somehow I ended up on the vCluster site and decided to give it a try, as it can be a valid way of providing developers with on demand clusters for debugging or run CI/CD tests before deploying things on common clusters or even to have multiple debugging virtual clusters on a local machine with only one of them running at any given time. On this post I will deploy a vcluster using the k3d_argocd kubernetes cluster (the one we created on the posts about argocd) as the host and will show how to: use its ingress (in our case traefik) to access the API of the virtual one (removes the need of having to use the vcluster connect command to access it with kubectl),publish the ingress objects deployed on the virtual cluster on the host ingress, anduse the sealed-secrets of the host cluster to manage the virtual cluster secrets. | ||
