jax

jax , 14 days ago

Desktop: Windows XP

Linux: Probably Raspbian on a Pi 2 b

Tech has come a long way since then lol

jax , 1 month ago

Currently using Nextcloud AIO and it’s pretty decent, though I’ve got 16 vCPU and 32 GB of RAM allocated to it right now, though it’s only using 10% CPU and ~7 GB of RAM at the moment.

I think it takes a while to warm up once you start adding data to it, especially depending on the plug-ins you add and amount of data.

jax , 1 month ago

What’s everyone’s workflows with these systems? Do you catalog both physical and digital documents? Where do you store the documents?

jax OP , 1 month ago

Oh, I know I could get them to run with enough work. I just don’t have that much time to spend on initial implementation and upkeep of the charts.

I’m using FluxCD, which I believe can do deployments of plain Kubernetes manifests, but that still requires a decent amount of overhead to keep up to date.

jax OP , 1 month ago

Yeah, that’s the pain point - building and maintaining the charts.

Also, I know the charts likely wouldn’t have to be super complex, but I’m used to working with Bitnami’s charts that are massively complex - I just don’t have the time to go that in-depth.

jax OP , 1 month ago

That’s actually super helpful! I haven’t done much custom Helm chart-ing, and was kinda lost where to start. That really helps break the process down, and the tip about skipping state to start is very wise.

jax OP , 1 month ago

I think both of the ones I mentioned have docker-compose files, which I think I can convert with kompose convert? I guess from there I would follow your steps and then start parameterizing it once it’s running properly.

Thanks! I think I’ll start trying out PixelFed tomorrow.

jax OP , 1 month ago

I’ve seen that around, but I prefer to run my own services instead of relying on a ready-built system like that. I find they don’t offer that much customization options usually.

jax , 11 months ago

🤮

jax , 11 months ago

Just because it’s not public facing doesn’t mean that it’s not an issue. It might be less of an issue, but it is still a massive vulnerability.

All it takes is one misconfiguration or other vulnerable system to use this as a jumping off point to burrow into other systems. Especially if this system has elevated access to sensitive locations within your network.

jax OP , 1 year ago

Ahh, I didn’t get that far in the docs, but seeing as there are no (that I can tell) post limits, running a blog on Lemmy would work pretty well with a bit of a UI change.