I'm going to spin up some dev resources to see if I can figure out how
to compile the latest. In the mean time, this is doing what I want and
is going to get deployed.
I kept hitting errors like:
Something went wrong. Here's the specific error message we encountered: Operation failed after 3 attempts: 400 {"type":"error","error":{"type":"invalid_request_error","message":"\"claude-opus-4-20250514\" is not supported on this API. Please use the Messages API instead."}}
I believe from https://github.com/danny-avila/LibreChat/discussions/7554
that I may need to update the version of librechat I'm running.
With these changes I have librechat running and being properly
reverse-proxied and I can login via SSO. I was not able to get a
reasonable response yet from Claude.
I'm probably not going to use it, and prefer librechat instead.
I mostly gave up on it because I couldn't make heads-nor-tails of their
SSO settings. It just says "authelia=true" - that's not enough to
configure any SSO, even Authelia.
I probably misunderstand what Sillytavern fundamentally is.
The 'user' config was only used by this fish module, and became silly
as soon as I had to duplicate it to the git module. Instead I set it
once in the home config and reference it.
In addition this change includes enabling the fish shell. This makes it
possible to do things like set session variables, which I'll do in the
next commit.
Without this I was getting errors like:
> error: flake 'flake:nixos-anywhere' does not provide attribute 'packages.x86_64-linux.nixosConfigurations."digitalocean".config.system.build.diskoScript', 'legacyPackages.x86_64-linux.nixosConfigurations."digitalocean".config.system.build.diskoScript' or 'nixosConfigurations."digitalocean".config.system.build.diskoScript'
I'm not sure why.
Most things work on this commit, except the integration between
collabora and seafile. I think it might be related to the timezone
change I made and a lack of access_token being passed in the URL.
I'm going to test that with a reboot. But first, checkpoint!
We put it in the pod because I don't know how to make it accessible to
things in the bod without binding all host addresses. There's probably a
sophisticated way to do it correctly, but I don't want to figure it out
yet.
