but the image it self is only using runserver, which means it is only for
dev-server.
The requirements.txt can be part of connected volume. So the image contains
only django and configured server.
On Tuesday, February 26, 2019 at 5:28:14 PM UTC+2, Tom Forbes wrote:
>
> There never was an offici
Thanks, Josh. I will be cautious if I ever get to taking this on.
On Tuesday, February 19, 2019 at 9:55:49 PM UTC-5, Josh Smeaton wrote:
>
> To add - there's definitely appetite for this feature, but it's a
> difficult one, and no one has stepped up to do it.
> There are DEP drafts that cover pie
There never was an official Django image, it was an "official docker"
Django image that they maintained. The page image page explains why it was
deprecated: https://hub.docker.com/_/django
For most usages of this image, it was already not bringing in django from
> this image, but actually from
On Tuesday, February 26, 2019 at 8:39:34 AM UTC+1, Alexander Lyabah wrote:
>
> I found out that official django container is deprecated. Why you don't
> want to support it?
>
There was never one to begin with.
--
You received this message because you are subscribed to the Google Groups
"Dja
