That’s not what ‘keyless entry’ means. You still have to open your door, you just don’t need to press a button to unlock it first.

If you’re hosting websites and not applications, perhaps you can use SSGs like Hugo/Gatsby. You could deploy your site in a bucket and put cloudflare in front. They can also be used on your own server of course. If you are hosting applications and want to keep them on 4g, you could put a CDN (CloudFlare or …) in frint of it. That would cache all static resources and greatly improve response times.

If you’re hosting websites and not applications, perhaps you can use SSGs like Hugo/Gatsby. You could deploy your site in a bucket and put cloudflare in front. They can also be used on your own server of course. If you are hosting applications and want to keep them on 4g, you could put a CDN (CloudFlare or …) in frint of it. That would cache all static resources and greatly improve response times.

Containers are bad hmmkay… cause… cause… they’re bad… hmmkay

Portainer + caddy + watchtower, this will give you the benefits of containers without the complexity of Kubernetes. As someone who professionally works with Kubernetes, I agree with what other people have said here: “only run it if you want to learn it for professional use”.

Portainer is a friendly UI for running containers. It supports docker compose as well. It helps with observability and ops.
Caddy is an easy proxy with automatic Let’s Encrypt support.
Watchtower will update and restart your containers if there’s an update.
(Edit: formatting)

It’s not efficiency that makes people prefer democracy.

I would suggest using Caddy. I think it’s a little simpler than Traefik and can automatically handle LetsEncrypt SSL/TLS certificates for you

My 2c, buy RPi’s because what makes them so great is the availability of drivers and information. You will end up paying with your time if you try to save some money up front. I had several OPi, one randomly started throwing errors. After several reinstalls with various sd card, the information I could find was that the SoC itself was causing the errors. Also getting any hardware to work with it is just a major pain, driver support is severely lacking. Support for the Linux versions is community driven, so you’re dependent on Armbian maintainers. If you have a very new or an older board, you’re probably out of luck when you want to do anything outside of Linux. Example, I could not get a camera and BT module working. I later bought a RPi4 and had the same hardware working within hours.

If this is all based on just the teardown of a cable than the article is just speculation. If it really lacks all additional pins this is just malicious compliance on Apple’s part. “Oh you asked for a usb-c connector EU Commission? Here it is”.

deleted by creator

The article states that the iPhone (the device itself) will be limited to USB 2.0 speed. Do you have information otherwise? Also limiting the speed does not mean it will not support the additional protocols that USB-C would allow for. I believe why people are making a fuzz over this is that people with iPhones want to be able to do large exports/backups/imports. Specifically those that use the devices professionally. In those cases you would want all the speed you can have, and this feels like an arbitrary limit set by Apple because they don’t want to fully comply. Perhaps there are good reasons due to heat issues in the storage controller.

:x also writes (same as :wq). :q! is force quit. If you accidentally made changes then :q will give an error and :x will write those changes. So :q! Is you safest bet if you need to gtfo.