What gold!
The essential piece of your logic is here:
> Enforce a development process that ensures that (roughly speaking) all
> database changes result in a new column, and where the old cannot be
> removed until a later update cycle. All migrations populate the new column.
I assume that "en
I've come around to your way of thinking now that I'm considering
django-storages and AWS deployments.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-us
This seems related to my question on how to do Blue/Green deployments. If
you want to build a real CI/CD stack for it and you want the previous
version to be safe and the cut-over to the new version to be consistent,
durable, and reasonably atomic, then you have some work to do.
--
You recei
My organization is moving into the AWS cloud, and with some other projects
using MongoDB, ElasticSearch and a web application framework that is not
Django, we've had no problem.
I'm our "Systems/Applications Architect", and some years ago I helped
choose Django over some other solutions. I st
4 matches
Mail list logo