that’s “globally recognised”? Run from them as fast as possible if you would any of your services to work
Well obviously yes, namecheap have been around a very long time and after GoDaddy (the default in the early 2000s for most people) Namecheap became a kind of default. One would think that a company with an online presence going back over two decades, and one a relatively low number of domain registrars, is "globally recognised".
Whether they're "good" or even "passable" is another matter entirely, but without switching away from Google to Namecheap for a few months, one wouldn't have much of an idea. And now I know.
How many really decent email providers are there aside from Google? What's today's obvious choice? And will they last?
For making a static site that you're personally deploying, exactly why is Docker required? And if the Docker process will have to bring in an entire Linux image anyway, why is obtaining Python separately better than using a Python provided by the image? And given that we've created an entire isolated container with an explicitly installed Python, why is running a Python script via `uv` better than running it via `python`? Why are we also setting up a virtual environment if we have this container already?
Since we're already making a `pyproject.toml` so that uv knows what the dependencies are, we could just as well make a wheel, use e.g. pipx to install it locally (no container required) and run the program's own entry point. (Or use someone else's SSG, permanently installed the same way. Which is what I'm doing.)
Once the basic functionality was worked out in js (with a simple JSON schema and Lourm Ipsum text), I created a Samba share on the network, mapped it to her computer.
Her first post was an edit of the Lorum Ipsum markdown and some new images, and from then on she had a pattern to follow: add a directory with a markdown file and assets.
The NAS runs a Go program that generates a JSON file for the static site js, starts a http server for testing. She can access the http server over the network to preview the static site. If it's ok, she can trigger a git commit and push (with a click). She didn't have to learn anything (like Hugo or jinja), because markdown is kinda obvious. She has exactly the website she wants.
Of course, I had more work to do initially, coming up with the static site, the JSON schema and the go generator, but it was over a week of evenings. She's been happily adding to it regularly without my interaction.
And this, my friends, is why I (a mere DevOps / Cloud guy) "vibe code" with Claude.