This will take care of the other commenters point about having to manually subscribe to everything. I just had it pull the top 500 communities from the top two instances and I’m fine…
Diabetes Type II: You can lose your feet. You can go blind. The risk of cancer, stroke, and heart disease go way up. You can get kidney failure. There’s more, but it’s a long list of shit that can go wrong. You don’t want it.
Ok, thanks, guess I’ll stick with Ubuntu 20.04 for as long as possible, hopefully IPv6 support improves until then. I’m really surprised by the amount of IPv6 bugs in Debian, some of them even over a decade old, for example simply not being able to configure sssd without IPv4.
I think I misunderstood you. The one I was talking about was a bug in proxmox. If it’s an issues inside lxc, you can replicate the Ubuntu networking stack using nmcli or use systemd-networkd and resolved directly. It behaves identically as far as I know.
Assuming visual novels count as “games”, probably one of the best soundtracks I’ve ever run across is the one for EverlastingSummer. Both Silent Owl (Sergey Eybog) and Between August and December did amazing work on it.
Doing this, running on a VPS with 1GB of RAM perfectly fine. No whitelisting required but you will have to manually subscribe to everything you want to see, so such thing as a proper “all” feed since this only shows feeds that users of your instance are subscribed to. Subscriptions are a bit weird, you want to search for the full URL of a sublemmy, then try it again after some minutes for it to work since it has to be fetched first. The ansible playbook is ridiculously easy to use for deployment.
Mastodon is a different beast, from what I saw so far, this needs much more configuration effort for deployment.
For SBC, you can’t beat Raspberry Pi. The ecosystem is just there and the support outclasses every other board.
For hardware based on SBCs, Pine64 hands down. Devices like the Pinebook and Pinetab are SBCs in a hardware shell and as such should feel like cheap gadgets, but their build quality is excellent and these feel like premium devices. I have just started messing with the Pinetab 2 and it feels like a device 3x its price, to the degree that I don’t mind that the drivers and software for it are still a work in progress.
God, tell me about it. I did not fully appreciate the Pi until the Beagle, which has an ecosystem that seems to be following some branch of chaos theory when it comes to organization.
Pine64: I honestly regret I didn’t follow up on this more before now because I had no idea about the Pinebook and Pinetab and I’ve been thinking about diy tablets, since diy laptops are still–really not a thing and it occurred to me just recently to see what’s up with open source tablets. I use a kindle for reading but when I went back to school, most of my books aren’t really Kindle-compatible so I bought a Galaxy Tab Ultra (10 inch, as eyesight) both so I could use Kindle search functions and a readable text size and so I blow up the diagrams. It wasn’t as horrendously expensive as it could have been because, like my phone, I trade in yearly to upgrade, not because i need to but because–depressingly–it’s more affordable when I can get max trade-in value and watch carefully for Samsung’s random discounts.
So yes, I am excited about this. My tablet is a very different use case from my phone (which no, no way to switch to open-source or Linux there at this point); migrating to an open source tablet is actually a possibility. So very cool.
Do yourself a favor and nab Pinetab 2. The wifi and bluetooth drivers aren’t ready yet (you’ll need a dongle or to tether a phone,) but that’s part of the fun: you can join the Discord channel and watch the discussions and commits happening in real time.
That’s because they sell at community prices for little to no profit, either at cost or close to it. They’ve talked about eventually trying to get their prices into retail outlets with a retail markup, which would also pay for retail-level support rather than community support.
In other words, if you buy community, you’re buying just the hardware, and the community provided the software.
I use podman for almost everything. Especially since it’s working rootless. BUT I am also clearly swimming against the tide there. Everyone else in the company uses docker and I typically can’t just take their docker-compose setups 1:1 over to podman. First, because they often rely on having root and second, because they use docker specific hacks (like some internal hostname you can use to access the host from within docker). Since I am not a fan of docker-compose anyway, I don’t care that much … I would have built my own setup with docker as well.
On my server I have a lot less trouble with podman than I had with docker. I run quite a lot of services there, and the docker proxy (and sometime the daemon) always started to act up after a while, causing individual containers to no longer properly receive traffic and me no long being able to control them. With podman all of that just works. And I have systemd managing the container lifetimes instead of some blackbox.
I want full control over which containers launch when. I also typically have a different requirement in which network a container runs and I want to re-use existing databases instead of spinning up a new one for each service. I want specific container names. And so on.
You can tell which service depends on which in compose, you can create, specify and set networks and add containers to them, you can keep a central database and just add the network of it to your new services, and you can also specify a container name.
As I see it (and for my compose usage), everything you mentioned works in compose.
Besides, what is your alternative? Do you just use the docker cli? I personally found that to be way less flexible than compose.
You can tell which service depends on which in compose, you can create, specify and set networks and add containers to them, you can keep a central database and just add the network of it to your new services, and you can also specify a container name.
The point is, if I get a compose file, all of that is already wired up with expectations of the maintainer. When I start heavily modifying it, I end up with an unmaintainable mess. So I rather look into what the service(s) actually require and build it for my use case.
Besides, what is your alternative?
The CLI, yes. And for my own server Ansible. But the semantics of the ansible module are identical to the CLI. Knowing the CLI by heart gets me much further than knowing docker-compose by heart. (Actually, I would have to look into the manual for docker-compose all the time, while I can simply do podman --help to see what parameters it needs, if I forgot something.)
Compose is simpler, and has a much easier base use case, but we've found it more functional as a dev tool to get the service running before making a full deployment config, rather than as an effective production solution.
Developing against k8s would kill me. I want my services and debugger running locally and don’t want to deploy shit first. In my current local setup it doesn’t matter if I spin up a service as container (because I just need it doing its thing) or if I spin it up with debugger attached in the IDE because I am developing (or debuging) it. I can fully mix-and-match at nearly every layer of the system.
Our shared dev, stage and prod systems are also fully k8s. Not with helm though. For our own stuff we have an operator with CRD, so we can easily define our business services without much boilerplate and still be consistent across the teams. The different configs are built using kustomize as part of our CD pipeline.
My account was suspended because a bot mod from /r/justiceserved banned me because i had the gall to reply to a post from /r/joerogan that made it to the front page.
I had said Joe Rogan looked like Dr. Evil’s older brother.
Then when pointing out the irony of such a bully moderator move, they banned my entire account.
So i shall simply be content to watch Reddit eat itself and die.
I suspect speedometers are never completely accurate. So instead of an exact number, they’ll use a needle and you can guess how fast you’re approximately going
kbin.life
Active