trustchain-oc1-orchestral
/
idhub-docker
Archived
10
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
This repository has been archived on 2024-05-31. You can view files and clone it, but cannot push or open issues or pull requests.
idhub-docker/docker/orchestra.Dockerfile

141 lines
4.7 KiB
Docker
Raw Permalink Normal View History

new Dockerfiles for musician and orchestra orchestra: 1.28GB -> 848MB musician: 497MB -> 169MB
2024-01-26 02:44:56 +00:00
FROM python:3.9.18-slim-bullseye
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
# based on https://github.com/glic3rinu/django-orchestra/blob/master/INSTALL.md
# HOW TO RUN THIS
#
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
# 0. rsync -avhP root@109.69.8.140:/opt/orchestra orchestra
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
# 1. copy this Dockerfile into a dir containing orchestra, like:
# $ ls
# Dockerfile orchestra
# 2. docker build -f orchestra .
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
# 3. docker rm orchestra; docker run -v /Users/maymerichgubern/orchestra/orchestra/:/opt/orchestra -p 8443:443 -p 8080:80 -it --name orchestra orchestra bash
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
# 4. sed -i "s/ALLOWED_HOSTS = .*/ALLOWED_HOSTS = ('orchestra.pangea.org', 'localhost')/" panel/settings.py
# 5. service postgresql start; service uwsgi start; service nginx start
# 6. goto https://localhost:8443/admin/
#RUN apt-get update -y && apt-get upgrade -y
new Dockerfiles for musician and orchestra orchestra: 1.28GB -> 848MB musician: 497MB -> 169MB
2024-01-26 02:44:56 +00:00
RUN apt update && apt-get install --no-install-recommends -y \
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
postgresql \
cron \
nginx-full \
sudo \
ca-certificates \
gettext \
bind9utils \
wget \
expect \
wkhtmltopdf \
procps \
net-tools \
ssh \
wkhtmltopdf \
xvfb \
zlib1g-dev \
libcrack2-dev \
libxml2-dev \
libxslt1-dev \
new Dockerfiles for musician and orchestra orchestra: 1.28GB -> 848MB musician: 497MB -> 169MB
2024-01-26 02:44:56 +00:00
&& rm -rf /var/lib/apt/lists/*
# 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
# using binaries I avoid installing c compiler
# pyuwsgi -> src https://discuss.python.org/t/how-to-install-uwsgi-package-from-pypi/25082/5
# setuptools before installing requirements and the anyjson python package -> src https://stackoverflow.com/questions/72414481/error-in-anyjson-setup-command-use-2to3-is-invalid/74272722#74272722
RUN pip install \
"setuptools<58.0.0" \
psycopg2-binary \
pyuwsgi
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
# Clean up to reduce image size
RUN apt clean && rm -rf /var/lib/apt/lists/*
# celery pinned because big changes on periodic_tasks related API
# celery3.1 wont support > python3.9 (dependency with celery should be removed), celery3.1 won't support django4.0
# orchestra initially was using celery to run async tasks, but then switched to process/threads without MQ... but the dependency with celery was never fully removed :(
# django-iban wont support > 4.0 (django-iban is deprecated, replace by django-localflavor)
# django 3 cannot work https://stackoverflow.com/questions/59261254/no-module-named-django-contrib-staticfiles-templatetags
# RUN pip3 install \
# django==3.2.18 \
# django-fluent-dashboard \
# django-admin-tools \
# django-extensions \
# celery==3.1.23 \
# django-celery==3.3.1 \
# django-cors-headers \
# Markdown \
# djangorestframework \
# ecdsa \
# Pygments \
# django-filter \
# jsonfield \
# python-dateutil \
# https://github.com/glic3rinu/passlib/archive/master.zip \
# django-iban \
# requests \
# phonenumbers \
# django-countries \
# django-localflavor \
# amqp \
# pytz \
# cracklib \
# lxml
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
# this is to ensure django project is created on top of this working directory
WORKDIR /opt/orchestra/
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
# TODO maybe from here goes to docker entrypoint?
# TODO assumes that the project already exists, and in some cases that would be interesting
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-orchestra/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
# TODO fix this better in the repo itself
new Dockerfiles for musician and orchestra orchestra: 1.28GB -> 848MB musician: 497MB -> 169MB
2024-01-26 02:44:56 +00:00
RUN pip install -r requirements.txt
RUN pip install lxml==4.9.3
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-orchestra .
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 sed -i 's/lxml==3.3.5/lxml==4.9.3/' requirements.txt
# solves "No module named 'orchestra'"
RUN pip install -e .
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
RUN django-admin startproject panel --template=/opt/orchestra/orchestra/conf/project_template/
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 adduser orchestra \
&& sudo adduser orchestra sudo \
&& su - orchestra
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
ENV PATH=$PATH:/opt/orchestra/django-orchestra/orchestra/bin
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/orchestra/panel
COPY docker/orchestra.migrate.exp /opt/orchestra/panel
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/orchestra.entrypoint.sh .
ENTRYPOINT sh ./orchestra.entrypoint.sh
# RUN expect -f ./orchestra.migrate.exp
#
# #RUN sed -i "s/'HOST': '',/'HOST': '*',/" panel/settings.py
# RUN sed -i "s/^ALLOWED_HOSTS = \[\]/ALLOWED_HOSTS = \['*'\]/" panel/settings.py
# CMD ./manage.py runserver 0.0.0.0:9080
# EXPOSE 9080:9080
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
#RUN echo /opt/orchestra/django-orchestra/ > /usr/local/lib/python3.9/dist-packages/orchestra.pth
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
# TODO move this to entrypoint, with fakedata
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
# && su postgres bash -c 'psql -f <(zcat /opt/orchestra/orchestra_db_20230907.sql)' \
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 service postgresql start \
# && python3 manage.py setupnginx --user orchestra \
# && su orchestra bash -c 'python3 manage.py setupcronbeat' \
# && su orchestra bash -c 'python3 manage.py syncperiodictasks'