Hello Ludovic, I'm glad this little joke tickled you, sorry for being that childish but sometimes I can't help it (I don't see how anybody could feel rationnaly offended since this joke talking about me). In reality, I've just been automating Django deployments for 10 year. So, if it takes 50 years to be an expert in something, I'm definitely too young to be an expert in anything ;)
Yes I have package deployment automation, because I maintain more than 30 open source packages, most of them for Django, on PyPi alone, some on NPM. The reason it's not the point, is that my CM aims at automating deployment of django projects, not of "django projects that have added my poor django app that provides a fixed createsuperuser and a removeuser CLI". So, if i'm doing this automation again (and I am), it will be in the CM, **not** in an app, because in this case, it **doesn't make sense to do it in an app, it would just make my CM more incompatible with OOTB Django**. It's the third time I'm explaining this, please excuse me for giving up as from where i'm standing it seems nobody is able to counter that objection, but I really feel like it's being purposely ignored. We never have two deploys "one local one production", we always have "one local one staging one production" so that's three. Ludovic, nowadays in the DevOps world we don't "automate deployment of requirements.txt" anymore, we don't "compile a virtualenv on the target" anymore, because we have separated "build-time" from "test-time" and "deploy-time", thanks to containers. This doesn't need to "react to changes or user feedback", the needs have been the same for 10 years, add/remove users in an automated way. Currently, we're injecting code in django-admin shell. Oh what's that final line of your email you're accusing me of being passive aggressive :D I do not have any more energy for this contribution, I'll just add it to my little monster crudlfap because that's my layer for any new project, as I have exigence for Controllers to refactor view code, and working ForeignKey/FileField forms out of the box (that means JS), now is the time crudlfap also compensate for Django's lack of OOTB automation feature, despite how basic they can be. Case closed as far as I'm concerned. My apologies to all the community for being unable to defend this proposal. Note to self: if I couldn't defend something as basic and obvious as this, learn that I will never be able to defend any proposal. Keep up the great work overall, sincerely Have a beautiful day, -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAC6Op1_61ysHz%2BSR-kvHuw%2Bm8eN8r_b2FGx2LHuhDLpC5t37CA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
