I've wanted to do this for a while. Thanks for detailing your setup! I hope one day I find the time to try it.
I've also always yearned for more usability from just the command line.
There's no tui spotify client, is there? Maybe I should break out my mp3 collection again... I'm trying to think of what else I'd really need to not need a GUI machine for my day to day. Maybe email?
Lynx and other tui browsers are not usable on today's web. Maybe there's a subculture to find somewhere that also appreciates reader-mode / lack of javascript?
The number of times I’ve had to defend someone else’s customers let alone my own is exhausting.
And that dynamic is only allowed within close circles.
I’ve found once “the decision” is made, the bigger the subsequent meeting, protests are often swept under the rug.
On most occasions the worst part is that folks intentionally withhold information to get their way. And thats real hard to compete against without making an ass out of yourself, or losing the trust of others.
I’ve also always wanted this, but what I’ve realized after noodling on it a while is I’d really just prefer a way to use git, and push markdown documents to the Notes System.
I dont want a different system handling edits reviews and merges.
I just want CD to send my docs from git to a system that can properly host / give me the Doc-related features I need.
Sorry if I'm being thick, but why not just cache the response?
If you are guessing at the data anyway, what's the difference?
Why set up an entire speculative execution engine / runtime snapshot rollback framework when it sounds like adding heuristic decision caching would solve this problem?
Hey cool project! I had the same need, and solved it a very different way.
I set up a wireguard server on a publicly accessible VPS.
The neat part about using "lscr.io/linuxserver/wireguard:latest"
is that it allows my to codify the number of clients I need. This includes both endpoints and source devices.
The second thing I did, was separate out the "networking" bits from the "userspace" bits, meaning it doesn't matter what port the service is running on. The client can hit it.
Taking that one step further, I just combined the above with haproxy and set my application ports there. This means I can hit haproxy on "someport" inside the VPN and it'll forward to whatever service I've got configured on that "client" that haproxy can see on it's LAN.
Works great, currently running a simple web page off the whole thing, where you connect to VPS and it tunnels the actual HTTP connection into kubernetes in my house.
I was thinking about writing this all up one day, but there's some cleanup to be done. Oh well.
> punish the grumpy ones in favor of the people-pleasers, that this crap happens
This isn’t exclusive to technology, but I see this all the time at my large organization. As a grump, I have to pick which shitstorm to care about and spend my time chipping away at, which ends up being really draining.
To help with this, we began focusing a team of great folks with shared values, leaning in on modern operations/SRE best practices.
We started to have some real success with SDLC for our operations workflows.
That’s when management changed our teams direction. Good times.
For the first bit, all I can think is a compose file. Also podman can run k8s configs locally, which I personally hope all of that eventually washes into the same thing. It feels like we already have the tools to make this a "solved" problem, is what I'm trying to say. I just include an additional .env that the compose file pulls in so it's not committed to git.
For the second point, ok this makes a little bit more sense, I've heard of Codespaces or OpenShift Dev Spaces but I guess I still question the value of additional complexity on top of the container (a simple dockerfile in my mind) your vscode instance's terminal is running in.
I did something similar with Kubernetes, work has some OSE clusters that will generate DNS for you, it works great and the devs love using it. It’s a little bespoke but its simple and gets a lot of attention.
Plus since the namespaces preexist the workloads, we spin them up for the entire branch lifetime (times out after n days). Makes everyones jobs a lot easier.
Anything that helps shift lifecycle requirements and testing left has huge impact on DX.
I’ve been working on the same thing for a few months now.
Not only is it more customizable / less complicated than helm / other solutions, but GNU gettext is almost 30?! years old at this point, and environment variables are probably realistically double that age. They aint going anywhere anytime soon.
Plus I feel that more complex logic removes value from the configs we are building, and so am not interested in many other tools.
If the door is not closed and you shift into drive, you also get a very loud annoying beep and visuals.
Not only that, the brakes engage and the car LOCKS ITSELF IN PARK AND DOES NOT LET YOU DRIVE EVEN THOUGH THE SHIFTER IS IN ‘D’!!!
I pray the door sensor doesnt fail while driving on the highway, or theres never a situation that arises where the car needs to be driven regardless of the door being open.
On top of that, the door locks /trunk locks act very strange while the engine is running /driver door is open. Still dont have that figured out.
>technically unfeasible to guarantee "pipe size" bandwidth to all routes on the internet to all your clients
Yes I agree. But if I pay an ISP for a 10mbps link, I should be able to get 10mbps to their NOC at all times, and then each ISP would be able to vary prices based on peer connectivity. This is where competition would strengthen the internet backbone.
You are saying it's okay for ISPs to charge per packet rather than per pipe size. It is possible for ISPs to set up their network for guaranteed bandwidth (at least as far as the NOC you are connected to). But not doing so means they can continually squeeze more money out of their customers without added infrastructure costs.
Without firsthand experience, it's difficult to explain to someone that once I configure an access layer switch with 48 1gbps ports on it, and 4 10gbps SPF+ uplinks, it only costs me the price of electricity and physical storage to move 1 packet over it, or an infinite number of packets over it.
My problem with that is that once the pipe is installed and working, it only costs maintenance. I'm not sure what you are trying to say with your seedbox example.
Paying for ACCESS makes sense. It costs the ISP to have the availability to connect you up.
Paying for USAGE is disgusting. The way a network works, is that besides upkeep which is a small percentage of TCO, upfront cost scales with total bandwidth, not total number of packets one needs to move across a set of links.
Meaning if the ISP buys enough network equipment for 100 users to each have 10mbps of available bandwidth, they no longer have costs besides upkeep (maintenance, support, and replacing broken hardware). This is a SMALL percentage of upfront buildout costs. This large lump sum in the beginning has the potential to deliver the same amount of bandwidth ad infinitum.
Charging users for USAGE is DISGUSTING and is literally not fair.
This is a better analogy, but still not quite right.
This issue constantly comes up with keeping the internet free and open. Take the following:
The customer pays for their connection, say 10mbps over Verizon's network. Under a free and open internet, the customer is allowed to use that 10mbps that they PAID for in whatever damn way they please.
Why should I be subject to Verizon's idea of what my connection should be used for? Congestion happens, but a properly designed network means that the pipes are mostly free and available under normal circumstances to all customers for all the bandwidth they paid for. Doesn't matter how many devices I use on the other side of that connection, I bought 10mbps and I should be able to use that 10mbps the way I want.
I've also always yearned for more usability from just the command line.
There's no tui spotify client, is there? Maybe I should break out my mp3 collection again... I'm trying to think of what else I'd really need to not need a GUI machine for my day to day. Maybe email?
Lynx and other tui browsers are not usable on today's web. Maybe there's a subculture to find somewhere that also appreciates reader-mode / lack of javascript?
If so anyone please lead me to the promise land!