The DNS record must point to cloudflare, not the instance IP
The DNS record must point to cloudflare, not the instance IP
I’m glad that development is getting more stable, the regular updates with breaking changes were not so great.
That’s true, but might not really be a problem for most. Just set the jail time to something short (few minutes, maybe an hour).
I don’t think your brain can be reasonably compared with an LLM, just like it can’t be compared with a calculator.
It’s absurd that some of the larger LLMs now use hundreds of billions of parameters (e.g. llama3.1 with 405B).
This doesn’t really seem like a smart usage of ressources if you need several of the largest GPUs available to even run one conversation.
There is no way to be 100% sure, but:
I can and do self host, but I’m not willing to provide these services for free. I don’t want to be responsible for other peoples passwords or family photos.
Thats where good, privacy-respecting services come into play. Instead of hosting for my neighbours, I would recommend mailbox.org, bitwarden, ente or a hosted nextcloud.
The blog post contains an interesting tineline. Apparently, the first fix was not sufficient. So if you have updated Vaultwaren before November 18, update it again.
Copy of the timeline:
My HP has a 65 watt CPU built in, when it’s running at full load it is quite loud.
Small, 10 inch rack, with some 3D printed rack mounts.
Maybe try some TLS-based VPN? This should work almost anywhere, because it looks like a standard HTTPS connection.
Wireguard - even on port 443 - is special as it uses UDP protocol and not the more widely used TCP protocol.
I don’t think these two games can be reasonably compared. HL2 is currently free, while concord was a paid game.
I like it :) Can you provide a link to the sensors you used?
You‘re supposed to host this yourself.
Set the DNS cache time to 60 seconds.
Set the script to run on every host delayed by some time to avoid simultaneously accessing the API (e.g. run the script every other minute).
With this approach, you get automatic failover in at most 3 minutes.
I’d host it on both webservers. The script sets the A record to all the servers that are online. Obviously, the script als has to check it’s own service.
It seems a little hacky though, for a business use case I would use another approach.
OP said that they have a static website, this eliminates the need for session sync.
Your challenge is that you need a loadbalancer. By hosting the loadbalancer yourself (e.g. on a VPS), you could also host your websites directly there…
My approach would be DNS-based. You can have multiple DNS A records, and the client picks one of them. With a little script you could remove one of the A Records of that server goes down. This way, you wouldn’t need a central hardware.
For a start, try hosting something in your own home. A raspberry or an older PC or laptop should be enough.
My first projects were a print server (so I can print via wifi) and a file server. Try to find something that is useful for you.
Only start hosting on the internet when you’ve learned the basics and have more experience.
This sounds reasonable IMO. After all, there is still room for a cheaper 9060 / 9050 series.