Yes, the website is for prospective (and current) clients.
A small annoyance in startup circles is getting feedback about my website front page along the lines of "I didn't understand your hero, everybody should understand in one sentence what you do". Well, no, my clients will self-select as in not everybody needs to understand what "troubleshooting servers" or "devops" is :-)
There is def some luck involved, as in you don't know beforehand what's going to be successful.
"You find a problem in a niche, say accounting for plumbers, and build for that, then you just go and market to these people". It's way better to work on something you are familiar with and you like.
They have saved _more_ than two hours per dev and week. There's a compound factor and now code can be more reliable (less outages or emergencies fixing bugs) etc. Also having a sane working environment helps engineers not quitting, which is very expensive if they are replaced.
Suerte! Unrelated, growing up in Spain it always baffled me that identification was based on a photo on your DNI. Stories of siblings or even friends that had a passing resemblance to each other sharing DNIs was a common story.
hello, thanks for the feedback. Just deployed a new image that only checks for the objective, not at what docker network somebody uses.
It is hard to have a checker that eliminates both false positives and false negatives in general, but we always try to minimize false negatives and we failed initially here.
We have scenarios running on k8s, both on single VMs (the ones you can see in the scenario list) and we also have a beta/PoC k8s cluster where we currently run a couple of scenarios as single pod (a docker container) or as a full system (the "kubernetes playgrounds", which is kind of hidden while we test it).
Is this what you were wondering? we do have pending to introduce podman scenarios as well
Hello, SadServers guy here. Free VMs are sandboxed (no way in or out other than coming in through the proxy) for security reasons. Paid accounts have VMs with internet access and SSH access (and your pub key is added to all VMs for convenience)
This is similar to our experience migrating a SadServers k8s service; basically Hetzner is way cheaper and more performant than the big cloud providers BUT you have to take into account man-hours for the migration and be careful with missing services or ancillary tooling: https://docs.sadservers.com/blog/migrating-k8s-out-of-cloud-...
Big cloud provider (AWS, Azure, GP) is great for all the managed ecosystem; if you mostly only need raw computing (CPU, memory, bandwidth), then a provider like Hertzner makes a lot of sense (plus they have API and basic services like LB/firewall and object storage).
We at SadServers moved from big cloud managed K8s to Hetzner + Edka and it's an order of magnitude cheaper (obv some perks are missing).