Hacker News Reader

Comment by ej_campbell | Hacker News Reader

You likely also don't need to run Django yourself either: https://cloud.google.com/appengine/docs/python/cloud-sql/dja...

View on HN

The built-in Django libraries for Django on App Engine are severely outdated. I have new guides that just vendor in recent version:

https://cloud.google.com/python/django/appengine

However there are a lot of tricky issues with Django on App Engine so I would also look into Djangae:

https://github.com/potatolondon/djangae

As far as Kubernetes, the OP and I had some independent discovery and started working on similar material at the same time. I also have some Django/Kubernetes content, both CloudSQL (MySQL) and Postgres in Kubernetes:

https://cloud.google.com/python/django/container-engine (CloudSQL)

https://medium.com/google-cloud/deploying-django-postgres-re... (Postgres)

My biggest reason for running the database in Kubernetes is a) CloudSQL doesn't currently support Postgres and b) it's interesting. Seems like OP had similar motivations.

Obvious disclosure: I work for GCP.

Parallel explorer and OP here. :)

I cited your work as additional reading because I really enjoyed watching your talk on this recently! While I'd figured out a bulk of this stuff out, there were a few things I learnt from it too.

Oh cool, I missed your citation. I am still figuring some things out as well so I am going to check out what you've done.

Definitely happy to have you contribute to the ecosystem. It seemed like a content gap that I wanted to fill in, but at Google we would of course prefer to have a healthy external ecosystem of people writing content like yourself!

If you're running a vanilla Django site with no esoteric libraries with special requirements (like numpy/scipy that need compilers etc. to get installed), this is definitely the correct way to go. But if you do have non-standard requirements that fall out of the rails of your PaaS, you need to consider other solutions.

Reply on news.ycombinator.com