idhub-docker/docker/musician.Dockerfile

FROM python:3.11.7-slim-bookworm

WORKDIR /opt/musician

# reduce size (python specifics) -> src https://stackoverflow.com/questions/74616667/removing-pip-cache-after-installing-dependencies-in-docker-image
ENV PYTHONDONTWRITEBYTECODE=1
# here document in dockerfile src https://stackoverflow.com/questions/40359282/launch-a-cat-command-unix-into-dockerfile
RUN cat > /etc/pip.conf <<END
[install]
compile = no

[global]
no-cache-dir = True
END

RUN pip install --upgrade pip
RUN pip install wheel

COPY django-musician/requirements.txt .
RUN pip install -r requirements.txt

COPY django-musician .

COPY docker/musician.entrypoint.sh .
ENTRYPOINT sh ./musician.entrypoint.sh

#RUN python manage.py migrate
#
#EXPOSE 8080
#
#ENTRYPOINT [ "python", "manage.py", "runserver", "0.0.0.0:8080" ]
new Dockerfiles for musician and orchestra orchestra: 1.28GB -> 848MB musician: 497MB -> 169MB 2024-01-26 02:44:56 +00:00			`FROM python:3.11.7-slim-bookworm`
init with previous work this repo is a reinitialization with a change in the concept previous repo had git subtree of django-musician and django-orchestra, that was too static for our interest next approach is a script that pulls git repos, and that would be needed if you want to build everything, if not, just with the docker compose you would have enough for running the containers, hence, downloading the images from the docker registry 2023-10-10 08:07:46 +00:00
preserve docker build cache on orchestra musician produce docker build speedup - git checkout produce docker cache invalidation, do it when needed - use /opt/app PATH for the two containers - use two different layers: one to do the pip requirements, the other for the rest of the sourcecode 2024-01-24 00:05:37 +00:00			`WORKDIR /opt/musician`
init with previous work this repo is a reinitialization with a change in the concept previous repo had git subtree of django-musician and django-orchestra, that was too static for our interest next approach is a script that pulls git repos, and that would be needed if you want to build everything, if not, just with the docker compose you would have enough for running the containers, hence, downloading the images from the docker registry 2023-10-10 08:07:46 +00:00
new Dockerfiles for musician and orchestra orchestra: 1.28GB -> 848MB musician: 497MB -> 169MB 2024-01-26 02:44:56 +00:00			`# reduce size (python specifics) -> src https://stackoverflow.com/questions/74616667/removing-pip-cache-after-installing-dependencies-in-docker-image`
			`ENV PYTHONDONTWRITEBYTECODE=1`
			`# here document in dockerfile src https://stackoverflow.com/questions/40359282/launch-a-cat-command-unix-into-dockerfile`
			`RUN cat > /etc/pip.conf <<END`
			`[install]`
			`compile = no`

			`[global]`
			`no-cache-dir = True`
			`END`

			`RUN pip install --upgrade pip`
init with previous work this repo is a reinitialization with a change in the concept previous repo had git subtree of django-musician and django-orchestra, that was too static for our interest next approach is a script that pulls git repos, and that would be needed if you want to build everything, if not, just with the docker compose you would have enough for running the containers, hence, downloading the images from the docker registry 2023-10-10 08:07:46 +00:00			`RUN pip install wheel`

preserve docker build cache on orchestra musician produce docker build speedup - git checkout produce docker cache invalidation, do it when needed - use /opt/app PATH for the two containers - use two different layers: one to do the pip requirements, the other for the rest of the sourcecode 2024-01-24 00:05:37 +00:00			`COPY django-musician/requirements.txt .`
init with previous work this repo is a reinitialization with a change in the concept previous repo had git subtree of django-musician and django-orchestra, that was too static for our interest next approach is a script that pulls git repos, and that would be needed if you want to build everything, if not, just with the docker compose you would have enough for running the containers, hence, downloading the images from the docker registry 2023-10-10 08:07:46 +00:00			`RUN pip install -r requirements.txt`

preserve docker build cache on orchestra musician produce docker build speedup - git checkout produce docker cache invalidation, do it when needed - use /opt/app PATH for the two containers - use two different layers: one to do the pip requirements, the other for the rest of the sourcecode 2024-01-24 00:05:37 +00:00			`COPY django-musician .`

init with previous work this repo is a reinitialization with a change in the concept previous repo had git subtree of django-musician and django-orchestra, that was too static for our interest next approach is a script that pulls git repos, and that would be needed if you want to build everything, if not, just with the docker compose you would have enough for running the containers, hence, downloading the images from the docker registry 2023-10-10 08:07:46 +00:00			`COPY docker/musician.entrypoint.sh .`
			`ENTRYPOINT sh ./musician.entrypoint.sh`

			`#RUN python manage.py migrate`
			`#`
			`#EXPOSE 8080`
			`#`
			`#ENTRYPOINT [ "python", "manage.py", "runserver", "0.0.0.0:8080" ]`