xcjs

My go-to solution for this is the Android FolderSync app with an SFTP connection.

I mean, sysvinit was just a bunch of root-executed bash scripts. I’m not sure if systemd is really much worse.

Systemd was created to allow parallel initialization, which other init systems lacked. If you want proof that one processor core is slower than one + n, you don’t need to compare init systems to do that.

Of course!

The Docker client communicates over a UNIX socket. If you mount that socket in a container with a Docker client, it can communicate with the host’s Docker instance.

It’s entirely optional.

There’s a container web UI called Portainer, but I’ve never used it. It may be what you’re looking for.

I also use a container called Watchtower to automatically update my services. Granted there’s some risk there, but I wrote a script for backup snapshots in case I need to revert, and Docker makes that easy with image tags.

There’s another container called Autoheal that will restart containers with failed healthchecks. (Not every container has a built in healthcheck, but they’re easy to add with a custom Dockerfile or a docker-compose.)

It’s really not! I migrated rapidly from orchestrating services with Vagrant and virtual machines to Docker just because of how much more efficient it is.

Granted, it’s a different tool to learn and takes time, but I feel like the tradeoff was well worth it in my case.

I also further orchestrate my containers using Ansible, but that’s not entirely necessary for everyone.

You can tinker in the image in a variety of ways, but make sure to preserve your state outside the container in some way:

1. Extend the image you want to use with a custom Dockerfile
2. Execute an interactive shell session, for example docker exec -it containerName /bin/bash
3. Replace or expose filesystem resources using host or volume mounts.

Yes, you can set a variety of resources constraints, including but not limited to processor and memory utilization.

There’s no reason to “freeze” a container, but if your state is in a host or volume mount, destroy the container, migrate your data, and resume it with a run command or docker-compose file. Different terminology and concept, but same result.

It may be worth it if you want to free up overhead used by virtual machines on your host, store your state more centrally, and/or represent your infrastructure as a docker-compose file or set of docker-compose files.

I bought a used 2018 model over a new current model because of the lack of physical function keys.

Also, Dell, bring back Fn + Left for Home and Fn + Right for End!

Who looked at a great keyboard layout and decided, “I know! I’ll make this Developer Edition hardware more difficult to develop on!”

I’m using https://www.kavitareader.com/ with Moon+ Reader. Kavita supports OPDS feeds, which is perfect.

I’m using a combination of:

• The Boox Palma reader, though they have larger tablets if you prefer. I’m not sure about the others, but the Palma runs Android with the Play Store.
• Kavita to host my ebooks online.
• FolderSync with SFTP to sync all of my books ahead of time to my SD card.
• Moon Reader to add my Kavita server’s OPDS feed as an online catalog if I need to grab something manually.
• Calibre to manage and embed metadata.

PNG support lossless compression through deflation, but there are encoders that can apply a lossy filter to the image to make the compression more effective.

PNG doesn’t support lossy compression natively, to be clear.

Rust specializes in making parallel processing secure and approachable, so it’s going get used in problems where parallel processing and efficiency matter.

Rust is also now allowed to be used in the Linux kernel for the same reasons, which is exciting!

Sounds like a job for Ansible. ;-)

Of course! Here’s the documentation for the docker-compose module: https://docs.ansible.com/ansible/latest/collections/community/docker/docker_compose_module.html

It does rely on the recently-made-legacy docker-compose client, so for now it’s still required to install that. If you need some advice or pointers, let me know.

That depends on what you mean by container. I use it to orchestrate Docker containers for my infrastructure and then some.

I was going to recommend Ansible as well - documentation as code can never be out of date if you continue using it.

It doesn’t quite say that, but I think the meaning is essentially the same: “Don’t choose a name after a project unique to that machine.” - RFC 1178

For my homelab, I think that’s fine to do. I’m unlikely to have multiple Plex servers locally, for example, and if so, numerically naming them is fine - I provision with Ansible, and if I’m at the point where I’m having sequentially numbered hosts, they’ll be configured as cattle anyway. Also, having the names reflect the services a host provides makes it easier to match in my playbooks.

I think it’s a better scheme than turning to mythology, fiction, or animal species, which oddly enough RFC 1178 does encourage you to do.

I use significant hardware component or model:

• Z390
• AERO15

…or sometimes intended purpose:

• USERV - Ubuntu SERVer
• PlexBox - Plex Server
• NAS - NAS
• Runner - GitLab Runner
• MDEV - Mobile DEVelopment
• MDEV2 - Mobile DEVelopment, Version 2

I also have a Kubernetes cluster that ranges from K8S_0 to K8S_5.

I’m still using the old docker-compose executable - my Docker role is still installing it until the Ansible module catches up.