They should put that across the top banner on Audible.

If you use github pages, you can create, deploy, and host static websites for free. Only cost, if you want your own URL, is for a custom DNS name.

You can use their default Jekyll static rendering engine, and create the content using Markdown. And with github actions, all you need to update the content is create markdown, then push the change to the same repo. After a few minutes, the new content shows up.

https://pages.github.com/

Hugo can also be used, but it takes a few extra steps: https://gohugo.io/hosting-and-deployment/hosting-on-github/

You can also find 'themes' to customize the look and feel of the site, specific to the site generation tool.

If you want a lot of extra features, Docusaurus is pretty much as good as it gets, and you can set it up to push out to GH pages: https://docusaurus.io/docs/deployment

I wouldn't put any load on it until it was stained. At least two coats and a sealer.

OK, you wanted a conversation… :-)

I did read the post, but I assumed it was the starting point of a system or mechanism, not the end-point. Wanting to just run "docker compose up" is fine, but there is more to developing and deploying to production (and continuing post-launch).

That's why I mentioned the CLI. It lets you go from a simple local app (Django on sqlite) to a Docker one (postgres, celery, redis, etc.), to all the way out to the cloud (ECS/EKS/serverless lambda/RDS), without having to remember what commands do what or managing lots of separate docker-compose files.

I can see we are VERY far apart on how docker should be used in moving toward a production-ready system.

For one thing, recommending putting secrets inside docker-compose is an instantly disqualifying piece of advice. There's a whole 'secrets' section of docker compose that is there to prevent people from inadvertently including those in cleartext and baking them into images: https://docs.docker.com/compose/how-tos/use-secrets/.

Github itself has a secret scanning mechanism to prevent leakage: https://docs.github.com/en/code-security/secret-scanning/introduction/about-secret-scanning. For gitlab, there's also Blackbox or HashiCorp vault. Putting AWS key/secret inside a repo can be VERY expensive and open one to legal liability if the account is misused. Repeated infractions could lead to AWS banning one's account.

I really recommend you take down that part of your post, instead of proliferating bad practices.

As for the rest, to each their own.

Making way for a new race of hardened, pissed off acid-fish.

Good stuff.

A few things I'd change:

• A CLI to simplify local vs docker vs cloud operations. Reduces chance of operator error. Have had good luck with python click library.
• Moving config settings into separate JSON and .env files to avoid loading too many config and secrets in the docker-compose file.
• For AWS, I'd go with CDK. That way, cloud deployment is all in python (or typescript).
• For cloud, you can also package Django into a single lambda, with dependencies inside a lambda layer. Not sure I'd use it in heavy production, but for small apps, really handy.
• Inside Django settings, you can switch DB and services whether running local (sqlite, Redis), docker (postgres, RabbitMQ), or cloud (RDS, SQS).

Wish somebody would plot public chargers per 100,000.

Why is that car parked on the wrong side of the charger, taking multiple parking spots?

This could be big. The fact that it's sub-dollar, open-source, AND could be put on FlexPCBs opens up a whole lot of applications.

Only concern is the same as for RFID. They end up so cheap they're tossed into landfills or end up in waterways without a second thought. At least there, people are working on biodegradable solutions: https://bioplasticsnews.com/2020/01/12/stora-enso-sustainable-rfid-tag/

If the Flex-RV people address sustainability, they could have a real winner.

Thanks, fixed.

"It probably sounded better in the original German." -- Molly Ivins.

For those too young to remember: https://www.keranews.org/arts-culture/2022-03-25/remembering-the-biting-wit-and-sharp-political-takes-of-legendary-texas-journalist-molly-ivins

My favorite tell is when a write-up starts with a verbose explanation of given knowledge on a subject. Yes, we all know what 'World Wide Web' and 'Internal Combustion Engines' are.

Get to the f'ing point.

So many $$$$$$$$$$$$$, no doubt, for a single record in a database.

Plenty more...

https://en.wikipedia.org/wiki/List_of_defunct_retailers_of_the_United_States

Also:

https://en.wikipedia.org/wiki/List_of_defunct_department_stores_of_the_United_States

https://pi-hole.net/

I know of two L7/Principles planning to quit by January. People with a ton of experience.

Funny how the definition of a product 'announcement' has changed. It used to be when you could go buy it.

Now...

First they switched to the mini-spares. Then they got rid of them altogether.

If you're lucky, there are little filler canisters and a cigarette lighter-powered air compressor to let you get slowly to a tire shop. Sometimes, not even that. If there's a nail or a blowout, tow-truck city. Just hope it's not out in the middle of nowhere in the dark or in bad weather.

Can we add 'cars with spare tires' to the list?

Having to call a damned tow-truck just to get a flat tire fixed is not a winning move if you're trying to sell how much your car benefits the environment.