Alex Tomkins

Co-founder and Technical Director at a not-for-profit digital agency. A developer with an interest in Python, Django and Terraform.

GitHub: https://github.com/tomkins

Last Notes

2025-02-05 13:40:56 CET

- reply

I think the episode isn't fully uploaded - it's only 13 minutes long.

2025-01-04 16:01:26 CET

- reply

It's always one container maximum, with a small bit of downtime during a deploy:
desired_count = 1
deployment_minimum_healthy_percent = 0
deployment_maximum_percent = 100
A few requests will fail during the deploy - but it doesn't take too long.

2025-01-04 14:47:32 CET

- reply

Yup, that's pretty much how I've got some of our Django/SQLite sites setup in AWS:
litestream restore -if-replica-exists /database/django.db
sqlite3 /database/django.db "PRAGMA journal_mode = wal;"
Then run litestream, that then calls migrations and uWSGI/uvicorn after that.

2025-01-03 19:41:56 CET

- reply

You don't - it's one server only, with the database WAL (transaction log) being shipped to S3 for backup/restore.
You can run multiple Django processes to scale up on a single server, and of course get a server with more cores. The one limitation is that you can't have more than one process writing to an SQLite database at the same time... but you can have a *lot* of readers.
And as the database is local, the latency is super low.

2024-12-17 19:07:59 CET

- reply

Doubt there's much interest to decouple it (it's simple enough and it works, and isn't too special/advanced to justify it).
It's something you could replicate (or use form-designer as [@matthiask](https://hachyderm.io/@matthiask ) mentioned).

2024-12-17 18:48:13 CET

- reply

Part of me wants to shout - just use Wagtail!
It's not perfect, but the form builder is pretty good. Part of me wishes that it had a slightly more advanced form builder, as the Wagtail admin is way more flexible than the Django admin - and could pull it off.
But, it's definitely easier to use Google Forms for most people 😉

2024-11-23 12:47:47 CET

- reply

Oh yes, it's the fun of devops with AWS/Terraform.
It's the equivalent of learning two additional frameworks. Firstly learning how the AWS ecosystem works, what's the best practice for that, along with things that feel like they should be simple options ending up being additional configuration systems due to the flexibility they want to offer. Then learning how Terraform maps to that.
It's magic when it all works though!

2024-11-23 12:30:38 CET

- reply

Start off with: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/private-content-restricting-access-to-s3.html
That'll allow you to stick to "private" files in S3 by default, but with CloudFront being able to access them (best practice).
Then: https://django-storages.readthedocs.io/en/latest/backends/amazon-S3.html#cloudfront-signed-urls
Links to the right places if you do really want private media files rather than fully public URLs.

2024-08-27 14:42:37 CEST

- reply

Yup - I had some fun a couple of weeks ago dropping quite a few sites down to 10% of what they were previously recording.

2024-08-27 13:55:08 CEST

- reply

Out of curiosity, is there much of a difference between sampled/traced requests, versus other requests?
(Is the additional monitoring having an impact?)