Agreed. As someone that Dockerizes all of their Django development I can
speak to how opinionated such an image would HAVE to be.
It can certainly be done, but I don’t think it should.
There is also an implied security / maintenance burden so unfortunately
even if it were appropriate, it’s not ex
I think the point we are trying to make is that it’s fundamentally not a
good thing to try and distribute a one-size fits all docker image for a
specific framework.
For reference here is one you can use yourself:
FROM python:3
COPY requirements.txt .
RUN pip install -r requirements.txt
COPY . .
C
I can make a version for production use (in a week or two), for your
critics.
For example, based on Appache wsgi.
PS: maybe it is also worth to make a docker image for testing changes in
Django source?
On Wednesday, February 27, 2019 at 4:31:17 PM UTC+2, Jamesie Pic wrote:
>
> > most people cu
> most people currently lean towards a microservice architecture and therefore
> towards flask.
"according to the 2018 JetBrains Developer Survey" and some people.
Why start a project with flask in 2019 instead of Quart which or
Starlette is another question that I suppose is out of the scope of
t
I don't think that a Docker image would make local development any easier.
I also don't see how that is implied by the reddit post and it's comments.
Looking through the posts, I agree with the assessment, that most people
currently lean towards a microservice architecture and therefore towards
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
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
