/explore
|
You are here 
|
www.trickster.dev | ||
| | | | |
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. | |
| | | | |
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. | |
| | | | |
nickcharlton.net
|
|
| | | | | I recently completed a project for an assignment which had a mess of dependencies. It depends upon libgit2 and pygit2, both of which are a complete pain to get working. After it blew up in my face for the third time, I realised I was being silly and should go back to using Vagrant, and along with it, the configuration management tool, Chef. | |
| | | | |
gaurav.koley.in
|
|
| | | [AI summary] The article details how to set up a development environment on Windows using WSL 2, including installing WSL 2, Docker, and VS Code with the Remote WSL extension for seamless Linux-based development. | ||
