

Really looking forward to SSO support!
(They/She)
This is my main lemmy account.
Admin of lemmy.cloudhub.social
I can also be found elsewhere on the fediverse at @jax@cloudhub.social
Really looking forward to SSO support!
What’s everyone’s workflows with these systems? Do you catalog both physical and digital documents? Where do you store the documents?
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.
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.
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.
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.
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.
You’d have to talk to the your instance admin, they should be able to go into the database and fix your account.
I changed Kubernetes’ coredns config to forward *.sendgrid.net to 1.1.1.1 rather than my internal Pi-Hole servers, which did seem to help a bit.
Haven’t tried since updating to 0.18.0, so it could be an internal issue as well.
I’m using Kubernetes, not docker compose, so this doesn’t exactly apply to my implementation.
My problem with email was a transient issue in resolving “smtp.sendgrid.net” inside my Kubernetes cluster.
I think setting up a relay would resolve the issue for me, but I’m not sure.
Saying that, I thought I had resolved the issue, but I didn’t get an email notification for your reply. I don’t think my SMTP issues are fixed lol.
Awesome, that’s super helpful, thank you!
I guess I’ll also look into an SMTP relay. That could be useful I guess.
What’s the sql query you are using? And which table do you remove them from? (Looks to me they show up in multiple tables)
I feel like that doesn’t really resolve the issue at all… it is merely a workaround.
On top of this, would manually deleting the user from the database be a good idea? I’m assuming not.
I’ve been following their work on implementing this via their newsletter and it seems to be coming along nicely. Can’t wait for them to complete implementing it.