hosaka

joined 2 years ago
[–] hosaka@programming.dev 4 points 5 months ago (3 children)

AliasVault has its own built-in email server that allows you to create unique email addresses and receive emails straight in AliasVault. No third-party email service required.

I don't get how does that work exactly in a self hosted environment?

[–] hosaka@programming.dev 1 points 5 months ago

Currently just alpine with docker compose, but I initially wanted to use podman, this was before quadlets were a thing and I found it very cumbersome to configure the networking between containers, also recall having to use kustomize as an extra step, so I gave up and went with compose.

Now there are quadlets with podman, which seem to do everything I need but require systemd. I'd be happy to switch from openrc to systemd just for the sake of using podman.

[–] hosaka@programming.dev 2 points 5 months ago (2 children)

I'll finally be able to switch from docker compose to podman with quadlets on my server running alpine

[–] hosaka@programming.dev 6 points 5 months ago

GitLab LFS storage is mad expensive. I regret buying into it... We have an unreal engine project and the assets cross over 20GB, not raw assets mind you. I've self hosted perforce before and should have stuck with that

[–] hosaka@programming.dev 1 points 6 months ago

You would probably want to start with the openai-agents SDK in that case.

[–] hosaka@programming.dev 5 points 6 months ago

Forgejo has auto mirroring built in, it'll periodically sync the repos you add. The disadvantage is you have to add them manually. Initially I wanted a list of my started github repos synced to my forgejo instance and just added them one by one. A simple cron job might be enough to do that, but last time I checked github didn't have an API for fetching started repositories.

[–] hosaka@programming.dev 0 points 6 months ago

Isn't VST pretty much a wild west anyway? I wonder how much is this really gonna help to standardize the tools/plugins

[–] hosaka@programming.dev 3 points 6 months ago

Mainly use it as a documentation search for APIs I'm not familiar with, or when I'm not sure what options there are to approach a problem. I work with unreal engine a lot, so I'd get a few pointers from an LLM first, then go read the source code of those APIs and inplement the rest myself.

[–] hosaka@programming.dev 2 points 6 months ago

I guess it can go both ways, but I'd probably put nixos under minimal and experienced branch

[–] hosaka@programming.dev 3 points 7 months ago

That's a great analogy, I'm going to try to use it at my place, next time I need to explain tech debt

[–] hosaka@programming.dev 1 points 8 months ago

That sounds like a good alternative for me. I didn't use lidarr to pull in new releases, mainly to tag and organise the files on disk, I'd mostly import albums manually when I come across something I want. So I wanna drop an album in some import directory, get it tagged with listenbrainz data and placed in the right place. Is that achievable with beets?

[–] hosaka@programming.dev 1 points 8 months ago (2 children)

I've got the same setup and have been waiting for the lidarr cache API to get fixed but it has been taking ages. Are you running beets at the same time as lidarr and how does it compare functionality wise? Would you be able to switch from lidarr or are you planning to go back to it eventually? I realized that having to rely on stability of someone else's cache server is not ideal.

view more: ‹ prev next ›