Vagrant VS Brackets

Vagrant

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.

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

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/

Tools like Docker and Vagrant can be used to allow local environments to mimic production environments.

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

Someone should fork and maintain Vagrant with an MPL open source license:

https://github.com/hashicorp/vagrant

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...

Link to the wonderful people who discovered how to fix the stupidest live preview error in all of human history: https://github.com/adobe/brackets/issues/11519

Heh, just a month ago Adobe Brackets (another Atom clone) did the same https://github.com/adobe/brackets

Oh, that's a good point about the sunsetting. In Brackets's case, Adobe left it active in the hands of the community.

Live Preview in particular is one of the areas I had some fun working on. I worked out a way to do diff/patch to make it quickly and incrementally update the browser[1]

[1]: https://github.com/adobe/brackets/wiki/Research%3A-HTML-DOM-...

Brackets may be a free and open-source code editor from the owner of Photoshop, Premiere Pro, and other amazing software providers Adobe. it's a primary target for web development and particularly on web designing because it provides plenty of features for web designers like Quick edit, Quick Docs, Live preview, Autosave, JSLint, Preprocessor support, Open source, Extension, themes, and more. Its software is licensed under the MIT license and it's currently run and maintained by Github's open-source developers. Its GitHub repository is https://github.com/adobe/brackets. it was created with help of Electron JS(JavaScript). it's available in 38 languages like HTML, CSS, JavaScript. It supports lots of extensions like Beautify, Autoprefixer, Emmet. Minifier, ToDo, Bracket Gits, Brackets File Icons, Swatcher, and more. it absolutely was initially released on 4 November 2014 around 7 years ago. it's integrated with NODE JS, JavaScript, Adobe PhotoShop, Vizy, and more, and firms like Zenkit, Startlink, MaGIC, WorldGaming, NeoQuant, Core, OpportunityWork, and more are using it for her projects. it's lots of benefits like -

I think you just need to download this : https://github.com/adobe/brackets/releases/download/release-1.14.2/Brackets.Release.1.14.2.msi

I don't think there's a fix for this. This problem has many issue entries on github, and it will eventually get worked on at some point. However you could try this troubleshoot guide.

https://brackets.io/ as well as https://registry.brackets.io/ are already back again. Currently there are still some issues with SSL certification but as soon as these are resolved we should expect to get a working extension manager again. After that, the community will be able to transition to the new branch of Brackets (brackets/brackets-cont) most likely by some kind of patch.