Isn’t uv
being used as a package manager/resolver in rye
? I’m using rye
for my new projects and it’s nice because ruff
and pytest
are being unified in it too.
Isn’t uv
being used as a package manager/resolver in rye
? I’m using rye
for my new projects and it’s nice because ruff
and pytest
are being unified in it too.
I think people are missing the point here. The biggest problem was not that the update was bricking the machines, that could’ve happened to Linux/macOS/BSD etc. The problem is that the solution to the problem is to MANUALLY access the machine, get into safe mode and type some commands. This is insane. And you should be able to EASILY disable automatic updates for apps like that on Windows Server.
I’m using Poetry as well. But I really hope Rye works out so we can finally end this madness.
Oh yes, the good ol’ disk destroyer!
Holy shit, and this is from 2005/2006. It has only gotten worse.
Yep, definitely something wrong with the webserver 😅 Can you try this configuration?
https://nextcloud.domain.com {
reverse_proxy 192.168.1.182:443 {
header_up Strict-Transport-Security "max-age=31536000; includeSubDomains; preload"
header_up X-Forwarded-Proto {scheme}
header_up X-Forwarded-For {remote}
header_up X-Real-IP {remote}
}
}
You said that “originally, the Nextcloud server handled HTTPS with Let’s Encrypt at domain.com
” and now you are redirecting to 192.168.1.182
on port 443
. Is this Nextcloud server still serving HTTPS with Let’s Encrypt for domain.com
?
I’m asking because if you are using Caddy in front of that HTTPS webserver as a reverse-proxy, you will need to override the Host
header with the configured upstream address. Here’s the documentation.
I think it would be something like this (?):
https://nextcloud.domain.com {
reverse_proxy domain.com:443 {
header_up Host {upstream_hostport}
header_up Strict-Transport-Security "max-age=31536000; includeSubDomains; preload"
header_up X-Forwarded-Proto {scheme}
header_up X-Forwarded-For {remote}
header_up X-Real-IP {remote}
}
}
More than 50 redirects? Hmm, that looks weird.
What is the output when you run wget --spider https://nextcloud.domain.com
?
Could you try enabling cookies for cURL and pasting the contents of the cookiefile
here?
curl --cookie cookiefile --cookie-jar cookiefile --location https://nextcloud.domain.com
301 Moved Permanently
is usually not something that requires user intervention. Most browsers should automatically detect the 301 Moved Permanently
response code and redirect automatically.
What happens when you run cURL with the --location
flag?
curl --location https://nextcloud.domain.com
Yeah, I wish Nextcloud focused more on the file manager side of their applications. I was using it on my TrueNAS instance and it seems like an unfinished product. E2EE is not enabled by default and looks like their implementation is not perfect either.
Wow, last time I checked logseq it was not that good. I hope they introduce their Logseq Sync eventually.
I just tested it and it looks amazing. I wonder if there are any templates for a Bullet Journal. This software is insane feature-wise, a lot of things to play with.
I think this pretty much sums it up: https://mastodon.social/@hynek/113094547139925962