fluxd VS Vagrant

Well it’s similar to AWS in that you can choose your resources. It’s way overkill for a portfolio website, but it’s also great practice for packaging using docker (required) and virtualization basics. You could probably keep your site running for years for less than $2 with lots of resources. runonflux.io

I think this might be similar to Flux: https://runonflux.io/

runonflux.io

A decentralized cloud kind of already exists. It’s tied to a crypto project called Flux. Haven’t tried it yet, but from what I’ve heated renting out your capacity can actually be paying pretty well (that was during the time when crypto was not as low as it is now).

Thought this community might be interested in Flux offering decentralized hosting of Wordpress, completely run by their 15k node operators. Check out more details here: https://runonflux.io/

Well you have to publish your docker repo as public to get your dapp whitelisted, this poses a problem for intellectual property and anyone wanting to deploy sensitive data. If you don’t have a need for protecting IP or sensitive data, you might consider runonflux as a viable competitor.

That’s because those users were failing benchmarks. If they were using decent hardware with decent bandwidth, they’d reap the rewards. Users that try to use duct tape and bubble gum for their node won’t get payouts, simple as. Personally my Cumulus nodes earn me more consistently than anything. I also run a app on runonflux and have zero complaints, it has eveything AWS has without the bullshit.

Yea, if I could only get in. I've tried the link on runonflux.io and it doesn't work. I've tried through the Discord.com web site and the Discord app. Tried this on 3 different computers. Even sent a tweet to Daniel Keller and so far no response. You would think other people are having the same problem getting into their Discord page.

To be honest, it’s something I don’t use or care about. I just backed up some photos to see it work and wasn’t impressed. I do have a dapp deployed on flux, the runonflux service is a major game changer in my opinion.

If it can be composed as a docker container, it can runonflux

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