Dangit, copy-pasta from an unrelated comment. Fixed.

“There’s always money in the banana stand.”

https://m.youtube.com/watch?v=UuHILqDIvis

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

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.

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).

MMT: https://www.vox.com/future-perfect/2019/4/16/18251646/modern-monetary-theory-new-moment-explained

They’re just trying to learn his dance moves.

It’s reposted on HBO Max on Sundays without commercials.

I’ve caught the first two episodes. Mimics some of the British version’s games: caption competition, fill in the blanks, etc. It has more of the early Angus Deayton vibe (single host for each show). The host, Roy Wood Jr. is a comedian along with the captains, so it’s more of a 1+2 show, whereas Angus always played the straight man. Also, the whole scoring point count artifice is missing.

So far, has had some funny bits and very timely for an election year. Worth watching, IMO, as long as you don’t compare it to the current version of the British original.

The problem with Chinese EVs is that they show it’s possible to innovate, keep prices down, and mass produce.

Ford, GM, even Tesla, are spending all their time whining about how it’s just not possible to compete. They point the finger at worker wages, instead of improving engineering and design, materials, manufacturing processes, and not chasing stock-market gains.

Stop making $70K SUVs and start making $20K Taurus and Escort EVs. You did it once. You can do it again.

https://youtu.be/tANavEbnKsU

Finland edition, where it apparently started. Action starts at 4:20m in.

Good, wholesome fun.

Anyone who has played the ‘Risk’ board game has an idea what the next moves should be.

Where you rotate so far right you end up at the left.

One Docker env variable and one line of code. Not a heavy lift, really. And next time I shell into the container I don’t need to remind everyone to activate the venv.

Creating a venv in Docker just for the hell of it is like creating a symlink to something that never changes or moves.

I can think of only two reasons to have a venv inside a container:

• If you’re running third-party services inside a container, pinned to different Python versions.

• If you do local development without docker and scripts that have to activate the venv from inside the script. If you move the scripts inside the container, now you don’t have a venv. But then it’s easy to just check an environment variable and skip, if inside Docker.

For most applications, it seems like an unnecessary extra step.

Once they get Threads support, their target audience will be the non-Twitter universe. This would make it easier for businesses, governments, journalists, and non-technical folks like influencers and celebrities to switch out. That’s how you get mass adoption.

I just tried it last week. Good start. Lots of promise.

That looks great. A lot of places just plonk the Chashu in there. Toasting it is extra bonus.

Wait until AGI!

AGI: Yes.

Wait until the sentient robots!

Sentient robots: Yes.

Wait until biological…

Biologics: Glub, glub. Yes.

I actually like it when these code helpers guess from one line what the rest should be and suggest it. It’s even more fun when it keeps guessing and the suggestions get progressively more whacky. Then they just start making completely unrelated shit up.

Once you say no, it goes back to the beginning and meekly repeats the very first suggestion, like a scolded puppy.