Ansible vault. All my config files and scripts are deployed with Ansible. Usually they are pushing those into a file or environment variable but if you scope permissions narrowly and don’t run services/containers as root you should be somewhat safe. If someone has filesystem access you’re already in big trouble.

Instead I’d focus on keeping your attack surface as small as possible. Keep services behind a VPN or segment public facing services to a separate VLAN or docker network.

Back in 2016 or so you could get a RaspberryPi 3 for $35. Add a $5 power supply, $5 SD card and $10 case (or 3d print your own) and you’ve got a nice little piece of hardware for running a tiny project at home for ~$50. More than enough for hosting some simple web services, backup software or something like Home Assistant.

Plus it was popular (which makes it even more popular). It’s always been very easy to find guides written specifically for the hardware, despite it’s limitations.

I think the value proposition has been dropping steadily though. They cost more, are hard to find and there are now a lot more competing SBCs on the market. RaspberryPi still has name recognition though, for now.

There is a community Ansible module for the Uptime-Kuma API that I’ve been trying to get working so I can trigger the maintenance window when I run my playbook to update services but I haven’t quite figured it out yet.

I’m in the same boat though, I start updating containers and my slack channel blows up for like five minutes straight.

I’ve got Uptime-Kuma internally for watching all my internal services and then I’ve got one running on a VPS that watches all the external services and public endpoints.

Such a great project and so easy to use…

FreeDNS requires you to log in to their website once a month or so to keep your DNS name active or they will revoke it. DuckDNS doesn’t require that. It’s free and it works. I set it up forever ago and never have to touch it, with FreeDNS I was risking losing my name or having my services go down if I missed their nag email.

I’m starting to think we just need to rebrand green energy projects to sound more like a tech concept to trick people into liking it more.

It’s not solar, it’s LightWave.

It’s going to be really difficult to get most people used to the idea of decentralized federated services.

I think a combination of 3d animation and ‘ai postprocessing’ is probably the most effective result.

As much as I respect the rights of extras, they are expensive and easier to replace than lead actors. Disney already has things setup so extras never have to be on set with your lead actors, although you get a lot of backgrounds with ‘people just walking back and forth with no purpose’, but a bit more effort will mean those prefilmed backgrounds wont even require human actors, they barely do already.

ansible-nas

Wow, yeah this is exactly the sort of roles/playbooks that I’ve been building. I’m definitely using this as a source before starting my own from scratch. Thanks for sharing.

I’m actually doing both right now since I had quite a huge compose file that I haven’t converted to ansible yet. The biggest frustration I have is that there doesn’t seem to be an ansible module that works with compose v2 (the official plugin) which means I’m either stuck on the old version of compose or I have to use shell commands to run stuff like ‘docker compose up -d’.

One nice thing I’ve gained though is for services like Plex. I have an ‘update’ playbook that I use and it will check to see if Plex is actively streaming before updating the container which isn’t something I could do easily with compose.

Hahaha, I’ve been using ChatGPT in the exact same way. It requires a bit of double-checking but it really speeds things up a lot.

I’ve started replacing my docker compose files with pure ansible that is the equivilent of doing docker run. My ansible playbooks look almost exactly like my compose file but they can also create folders, set config files or cycle services when configs are updated.

It’s been a bit of a learning process but it’s replaced a lot what was previously documentation with code instead.

I sharewared my firmware and got malware.

I’d recommend Duck DNS over Free DNS these days.

And Wireguard over OpenVPN.

But yes, this is the easiest free way to stand up a solid website. Only other thing I’d add is to put sites and services behind a reverse proxy. Typically I’ve used Nginx but I’m quickly becoming a Caddy convert.

I believe this has more to do with pict-rs than Lemmy (the image handling back end that Lemmy uses). I’m struggling to find specifics on this from my phone right now though.

I think Web 2.0 is coming to an end because we’ve seen a decade of web sites and services balloon to enormous sizes with absolutely no sustainable business model. They finally peaked with their userbase, there is nowhere else to grow. Now it’s time to start making money. So how do you do that without ruining the experience and driving everyone off to the next big thing?

Not my problem I suppose.

Flatpaks are here to stay but they can exist alongside traditional packages.

I never really cared about them tacking on a bunch of useless shit on top of Reddit. As a third-party-app and old.reddit user I kind of figured that if they monitized that piece and let me hang out in the underbelly then it wasn’t really a problem. Why not have the normies subsidize the denizens of the old reddit, it’s not like we aren’t using adblock anyway.

But now that they’ve killed off the API it’s only a matter of time before the come for old.reddit so I’m out before they get around to it.

I think you’ve just described the nature of copyright law, which is effective in some ways and ineffective in others.

I loved my Asus graphics card… Until it died.

I also loved my Asus Android tablet… Until a hardware problem that made it slower over time even after reformatting it thus eventually making it unusable. (Technically Nvidia’s fault I guess).

In theory their stuff is really great, but yeah I have definitely been burned by Asus in the past.