Revision 78d45fbe451629585fb851931d740580f7ea66aa authored by Paweł Kotiuk on 02 October 2023, 07:20:14 UTC, committed by GitHub on 02 October 2023, 07:20:14 UTC
I think a proper issue template based on simple form would make creating a proper issues easier for users. These templates can be checked on my fork of this repo: https://github.com/pktiuk/cvat/issues/new/choose ![image](https://github.com/opencv/cvat/assets/45544416/ffe2a64c-1cc6-4834-8ec9-9548144a21f5)
1 parent 4cdd68e
Dockerfile.ci
FROM cvat/server:local
ENV DJANGO_SETTINGS_MODULE=cvat.settings.testing
USER root
RUN apt-get update && \
DEBIAN_FRONTEND=noninteractive apt-get --no-install-recommends install -yq \
gpg-agent \
gnupg2 \
apt-utils \
build-essential \
python3-dev \
ruby \
&& \
curl https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add - && \
echo 'deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main' | tee /etc/apt/sources.list.d/google-chrome.list && \
curl https://deb.nodesource.com/setup_16.x | bash - && \
DEBIAN_FRONTEND=noninteractive apt-get --no-install-recommends install -yq \
google-chrome-stable \
nodejs \
&& \
npm install --global yarn && \
rm -rf /var/lib/apt/lists/*;
COPY cvat/requirements/ /tmp/cvat/requirements/
COPY utils/dataset_manifest/requirements.txt /tmp/utils/dataset_manifest/requirements.txt
RUN DATUMARO_HEADLESS=1 python3 -m pip install --no-cache-dir -r /tmp/cvat/requirements/testing.txt
COPY cvat-core ${HOME}/cvat-core
COPY cvat-data ${HOME}/cvat-data
COPY package.json ${HOME}/
COPY yarn.lock ${HOME}/
COPY tests ${HOME}/tests
COPY .coveragerc .
ENTRYPOINT []
Computing file changes ...