rcm
Vagrant
rcm | Vagrant | |
---|---|---|
19 | 116 | |
3,077 | 25,897 | |
0.6% | 0.5% | |
4.4 | 9.0 | |
about 2 months ago | 5 days ago | |
Perl | Ruby | |
BSD 3-clause "New" or "Revised" License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rcm
-
Rotz: Cross platform dotfile manager written in Rust
Are your per-machine branches mostly distinct, or do they share a lot?
I use https://github.com/thoughtbot/rcm and I find my dotfiles share _quite a bit_ in some respects (e.g. neovim config) but are drastically different in others (SSH config as one example) -- keeping things synced _across_ branches sounds very difficult. rcm handles this well, without branches, IMO.
-
Fulfilling a reader's request for my “dot files”
I use https://github.com/thoughtbot/rcm, which works smoothly and includes support for host-specific files
-
Guide me through!
I use thoughtbot/rcm to handle my github dotfiles. Super short version after installing, mkdir ~/.dotfiles Then go through your home directory (ie. ~/ ) and mkrc .bashrc and then do the same for any other files you plan on tweaking or have custom settings for. Most of these with be in ~/.config/ but some will be in ~/ . (ie. mkrc ~/.bashrc for your bash settings and aliases)
-
Don't Let Messy Dotfiles Ruin Your Coding Life! Try dotstow and Simplify Your Workflow Today!
Prior to catching the Nix brainworms and switching to home-manager, I mostly used thoughtbot/rcm.
-
Dotfiles Management
Personally I like (and use) rcm. Everything is still in a git repository, but has more features that work well for sharing across multiple machines.
-
Automatic setup
Check out https://github.com/thoughtbot/rcm
-
Ask HN: What are you using to organize dotfiles / dotconfig files?
I use rcm. It assumes you keep a separate (potentially version-controlled) folder at ~/.dotfiles or similar, and it provides a suite of tools for managing the symlinks.
https://github.com/thoughtbot/rcm
-
Thoughts on chezmoi
currently I am managing my dotfiles with rcm (ran by ansible). This approach served me well over the years but recently I stumpled over chezmoi.
-
Endevour OS with i3
Setup a Github/Gitlab account and find a dotfile manager you like (I'm using RCM - it can do more than I actually use it for).
- is there an ansible like tool in tcl?
Vagrant
-
How to Enable a Virtual Machine on Your Windows Laptop With Vagrant and Git Bash
Vagrant
-
Ask HN: Please recommend how to manage personal serverss
Take a look at Vagrant! https://www.vagrantup.com/ In my admittedly limited understanding I believe it offers closer to a nix like reproducable rather than repeatable deployments.
-
Software Company HashiCorp Is Weighing a Potential Sale
on the off chance one hasn't been tracking it, there were several "we don't need your stinking BuSL" projects when this drama first started:
https://github.com/opentofu#why-opentofu (Terraform)
https://github.com/openbao/openbao#readme (Vault)
and I know of several attempts at Vagrant <https://github.com/hashicorp/vagrant/forks> but I don't believe one of them has caught traction yet
There are also some who have talked about an "open Nomad" but since I don't play in that space I can't speak to it
-
Ask HN: Cleanest way to manage Windows OS?
It sounds like you're using Nix as a sort of configuration management solution. CM just isn't worth it for managing a single desktop IMO. It triples the effort for whenever you need to add or remove a package, as you must now add that also to your nix configuration. You're supposed to be able to make that back up in time saved restoring to the next machine, but inevitably the next machine will be different enough that you'll have to edit it all anyway. In the end I just got tired of trying to manage my own machine with infrastructure as code (though in fairness I was using puppet at the time not nix).
I keep a git repository with all my dot files in it[1]. This seems to work the best. It has a Windows folder as well, and I copy that out whenever I need to set up Windows.
A lot of people like using WSL but I hate how it hogs on my memory. Hyper-V is a terrible virtualization engine for consumer-grade use cases because it can't thin provision RAM. If I need to use docker, I will spin up a small Linux VM using vagrant[3] with Virtualbox[4] and put Docker on there. Vagrant is an extremely underrated tool in my opinion, particularly in a Windows context.
I use scoop for packages. Typically I will scoop install msys2 and then pin it so that it doesn't get blown away by the next upgrade.
Then I basically do all of my development inside of msys2. I can get most things running in there without virtualization. In my case that means sbcl and roswell for common lisp, senpai for irc, and tmux and nvim for sanity. Msys2 uses the pacman package manager and this is good enough.
All In all, I set up my Windows machine affresh after a while of not using it and it took me about 3 hours. Most of that time was just getting through upgrades though, I felt like it was pretty fast.
1: https://git.sr.ht/~skin/dotfiles
2: https://www.msys2.org/
3: https://www.vagrantup.com/
4: https://www.virtualbox.org/
-
A Developer's Journal: Simplifying the Twelve-Factor App
Tools like Docker and Vagrant can be used to allow local environments to mimic production environments.
- Is there any place where I can download an already configured Virtual machine? For example with Linux Ubuntu or Windows 10 preinstalled?
-
UTM – Virtual Machines for iOS and macOS
There's an open issue [1]. A scripting interface has since been added [2], and updated [3], so there's progress.
[1] https://github.com/hashicorp/vagrant/issues/12518
- Vagrant license changed to BUSL-1.1
-
HashiCorp Adopts Business Source License
Someone should fork and maintain Vagrant with an MPL open source license:
https://github.com/hashicorp/vagrant
-
Codespaces but open-source, client-only, and unopinionated
https://github.com/hashicorp/vagrant/blob/v2.3.7/CHANGELOG.m... ?
The changelog lists both improvements and bug fixes and there's even apparently some effort to port it away from ruby: https://github.com/hashicorp/vagrant/blob/v2.3.7/internal/cl...
What are some alternatives?
GNU Stow - GNU Stow - mirror of savannah git repository occasionally with more bleeding-edge branches
Packer - Packer is a tool for creating identical machine images for multiple platforms from a single source configuration.
yadm - Yet Another Dotfiles Manager
Ansible - Ansible is a radically simple IT automation platform that makes your applications and systems easier to deploy and maintain. Automate everything from code deployment to network configuration to cloud management, in a language that approaches plain English, using SSH, with no agents to install on remote systems. https://docs.ansible.com.
chezmoi - Manage your dotfiles across multiple diverse machines, securely.
QEMU - Official QEMU mirror. Please see https://www.qemu.org/contribute/ for how to submit changes to QEMU. Pull Requests are ignored. Please only use release tarballs from the QEMU website.
homesick - Your home directory is your castle. Don't leave your dotfiles behind.
Capistrano - A deployment automation tool built on Ruby, Rake, and SSH.
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
Puppet - Server automation framework and application
Chef - Chef Infra, a powerful automation platform that transforms infrastructure into code automating how infrastructure is configured, deployed and managed across any environment, at any scale
BOSH - Cloud Foundry BOSH is an open source tool chain for release engineering, deployment and lifecycle management of large scale distributed services.