I get a text pretty quickly.

I set this up before but ended up walking away. It works well but it always eats CPU generating the stream, which is a bummer if I’m the only user and not necessarily even going to use it once a day.

There’s a large group of folks here that swear by renting a VPS. A common argument is that when you fully self host and expose anything to the internet (incoming connections), you’ve always got some security risk you might not know exists.

A VPS offloads a lot of the low level security concerns to someone else (it’s the whole cloud sales pitch) and if someone breaks in, there’s little for them to steal (assuming you’re not putting anything personal and sensitive on the VPS).

The nice thing is that you can start with a small and cheap VPS and set things up and decide if you even want to self host, or to what extent. Then you have data to make a decision as to whether you need to upgrade to a better VPS, or port your setup to a local server (which you can now buy with a good idea of what sort of specs it should have).

On the flip side, you could also self host on whatever computer you have laying around (leave the laptop open) and play with some services there. If you decide you want to open it to the internet, you could just as easily port your local playground to a VPS and keep going.

I don’t think there’s anything in the self hosting world that really paints you into a corner.

Which password manager? I had the same problem with BitWarden until I found a buried setting to tweak each password domain. Maybe there’s a badly advertised feature in yours, too?

I run everything in docker. My docker volumes are all subdirectories under /media, which is the root of my NAS. If an app only needs something specific, docker only mounts, eg /media/movies. If the app needs many subdirectories (like backups), it gets the full /media mount.

All the docker data/configs are under /docker/volumes (eg /docker/volumes/jellyfin), and every container is configured with compose in /docker/docker-compose.yml.

The biggest hurdle for me was creating a sane docker-compose file that defines where everything lives. Once that is standardized, adding and maintaining your apps becomes easy.

If you’re very new to this, even a dumb LLM like ChatGPT can be very helpful to explain what’s inconsistent, redundant, or incorrect with your config. If you are lost I would strongly suggest this as a way to get oriented. But DO NOT copy and paste anything into the LLM containing passwords, tokens, keys, etc. if you accident do, change those keys before finishing up your project.

With docker there’s no duplication- you have one copy of everything you need and you just point each container at the same data. This makes it trivial to keep file consistent across your apps and doesn’t waste space.

The LubeLogger meltdown ticket is pretty goddamn funny.

Fileflows can probably be configured to do this. I only use it to convert everything to HEVC but it’s a node based workflow and you could roll in renaming and tagging.

what’s missing?

An AI disclosure for your app per the community rules, Claude.

This post requires an AI disclosure per the community rules.

On the flip side, if you’re vibe coding an app you should seriously consider whether it’s something you want to open source or make available publicly. There’s a social contract that comes with that.

I have 2 self hosted slop apps I build and maintain myself. I think people would genuinely get great use out of them.

…but then I’m inviting critiques and feature requests and am roped into supporting them so it’s not just a big pile of shit that wastes everyone’s time. And I don’t want to spend my limited free time making common sense improvements to improve it for others. I want to write a lazy Claude prompt with insufficient context, get it barely doing what I need, and then spend the rest of my time eating crayons and similar pastimes.

I use pangolin and traefik together and expose a few of my services that way. But not everything.

I slot services into categories based on:

• do I really need to be able to access this externally?
• …with full admin rights?
• what write/delete access am I granting?
• if an attacker got in, how much damage could they do with what they could access?

Then the service is either not externally open at all, secured behind pangolin SSO, or secured behind pangolin SSO AND that service’s native auth. Which is an annoying double auth, but I feel like it’s another layer of protection in case one of them gets a 0-day exploit.

Daaamn that was the nerd version of a KenM rejoinder! Well played.

568C (the C is for chaos)

Wire in whatever way they fall in by themselves.

Then rewire the pins on the NICs so they can communicate.

It’s not so bad once you level up your soldering skills.

Spend the extra 25k. It’s worth it in case you end up stuck trying to download a 62TB torrent and suddenly can’t!

Just found the other rule post. Looks great!

I want a community where people can use AI to help build a tool and be able to post about it here. But unfortunately, I’m just not seeing that. The AI-generated apps seem to be coupled to a drive-by, AI generated post (and comment replies) all full of em dashes and the standard Claude slop language.

So, yes, mandate an AI tag. Hold posters to it and remove violators, because it seems to always be the same class of “contributors” that are cosplaying as software developers.

Not sure if your rule changes are touching this, but the worst offenders I don’t want to see here are:

• posting and commenting text written entirely by AI
• not open sourcing or giving any visibility into their code
• adopting a paid model

The people doing that remind me of the people who would approach me 20 years ago saying “hey I have an idea for an app I want you to build and I’ll give you 5% of my company. It’s like Facebook for dogs, but I need you to sign an NDA before I say any more”.

Waddaya mean no cloud?

YOU ARE THE CLOUD NOW

Hey Claude! Nice work! Please spin up a new task branch and replace all text with random emojis. Deploy when done.

I have opinions, but none of them well enough formed to have suggestions on the new rule.

Try it for a while and see if it works! We know this community ain’t shy about sharing when something isn’t working for them!

I don’t care if an author is using AI in some capacity to write their app, but I draw a line when their posts on social media are also written by AI. There’s no human in it anymore.

The post was written by Claude. That’s its exact writing style I have to unpack every day during my day job.