Explore >> Select a destination
|
You are here 
|
www.trickster.dev | ||
| | | | |
www.hlfshell.ai
|
|
| | | | | tldr ROS/ROS2 environments are notoriously annoying to get into a repeatable, isolated dev environment. I write about my initial look into this problem, and some proposed solutions I tried. I present my imperfect solution using both Docker and VMs to wrap my whole dev environment with... moderate success. The Why ROS2 (I'll mostly focus on ROS2 in this post, but some of what I discuss here is applicable to a ROS environment as well) assumes that you'll be dedicating the entirety of the given system to ROS. | |
| | | | |
jiby.tech
|
|
| | | | | Like many developers, I keep track of my configuration files in version control, to make moving to new machines is simpler and share code with others. This process started out for my Emacs config files at first, but grew to consume other aspects: bash functions, git aliases... Since 2016, I have accumulated over 500 git commits. Now the dotfiles are tracked, the next biggest pain is to install packages and folder structures and obscure commands required to set up some subsystems needs which config files. | |
| | | | |
meka.rs
|
|
| | | | | Cloud Computing Basics 5 | |
| | | | |
blog.nuculabs.de
|
|
| | | Hi ?????, In this article I will talk about how to authenticate your applications to the Kubernetes API via the service accounts feature. Citing the Kubernetes docs, a service account for a pod: "provides an identity for processes that run in a Pod. When you (a human) access the cluster (for example, using kubectl), you are authenticated by the apiserver as a particular User Account (currently this is usually admin, unless your cluster administrator has customized your cluster). Processes in containers inside pods can also contact the apiserver. When they do, they are authenticated as a particular Service Account (for example, default)." ?? | ||
