This is a project python where you can write an install script from a template and write one or more _.conf.yaml with the instructions. So I search for a system for launch a command and update all and I find it: dotbot. So for some time I use a notebook ( a book where i write notes not a pc) where I log the change and this make some problems. And I need also some of this config on all my machine like the ssh’s config. I need to have my dotfiles synced and working on a Linux Machine (Arch), an Apple Machine and a Windows Machine… So not only I have multiple versions of configs but for multiple platform. Now some time has pass and I have a BIG FAT PROBLEM. Github suggest it was the 20 of Novembre the first version of the repo but I remember I was trying multiple idea of it and only later make a repo with clean code so It was sometime in November. With this article and some copy-and-paste from other dotfiles repo’s on Github I made mine So, in the end of the 2017 i find an article about dotfiles: Managing your Dotfiles If you ever use Unix based system you are familiar with dotfiles for configuration.Īny program has some of this file or folders laying arrount in your user root.Īnd many time it was a booring job to setup all your stuff before starting with all the work because I want the config to be the same every where I work. Open your settings.Using the same dotfiles on multiple computer in the easy way #dev #zeta target #coding #dotfiles This is enough to create a dev container, we can open the command palette on VS Code and run rebuild and reopen in container. You need to have the devcontainer extension installed in VS Code. We will just use the Microsoft provided golang image /devcontainers/go:0-1.18. Perhaps in a future post, I will go over how to use dev containers with an existing custom Docker image. Normally we would have a custom Docker image ![]() This is the default one generated by VS Code for Golang projects (when using the command palette). Set `remoteUser` to `root` to connect as root instead. Use 'postCreateCommand' to run commands after the container is created. , // Use 'forwardPorts' to make a list of ports inside the container available locally. Let’s go to our dotfiles repo which we will assume looks like: In this example, we will be using the dotbot-apt plugin. You have a dotfiles repo which uses DotBot, has profiles and has plugins installed. I will assume you are familiar with everything we’ve covered up to this point. One way we can do this is by using DotBot and a dotfiles repo. This will also mean it takes longer for the dev container to build. If every developer does that you could end up with a very large Docker file. I also don’t want to pollute the Docker file However one of the issues that can arise from this is how you get your dev tools/programs in the dev container.įor example, I use fish shell but lots of Docker containers default to using bash. Much like if we used docker exec -it ubuntu /bin/bash.Įxcept it provides a few nice conveniences such as copying (into the container) over the project files and our ssh keys. We do this by using a container (Docker), and we end up developing inside a container. One of the main advantages of dev containers is we can provide a “one button” setup for new developers. Devcontainers allow us to create consistent development environments. In this article, we will go over how you can personalise your dev containers. You can read more about devcontainers here. ![]() This article assumes you are already familiar with dev containers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |