richard/doccano - doccano - Gitea: RS Source Repository

python annotation-tool datasets active-learning text-annotation dataset natural-language-processing data-labeling machine-learning

8 lines

81 B

Raw Normal View History

Add Dockerfile As per https://github.com/chakki-works/doccano/projects/2#card-16406087, this change adds a Dockerfile for the project. The Python distribution used by the image can be specified via a build-time argument. This enables us in the future to for example run the tests on a wide variety of Python versions. In the future, the Dockerfile could be extended to for example leverage multi-stage builds. In this case, the first stage could run tests, linter, and so forth and then create a wheel or similar artifact via setuptools. A second stage in the build can then only include a minimal set of dependencies to install and run the artifact (e.g. using python-slim as a base image).

5 years ago

Ensure that server is started correctly in Docker Also: ignore files generated during application run which enables a better development experience in Docker with source mounts like `docker run -p 8080:80 -v $PWD:/doccano -it doccano`.

5 years ago

Add Dockerfile As per https://github.com/chakki-works/doccano/projects/2#card-16406087, this change adds a Dockerfile for the project. The Python distribution used by the image can be specified via a build-time argument. This enables us in the future to for example run the tests on a wide variety of Python versions. In the future, the Dockerfile could be extended to for example leverage multi-stage builds. In this case, the first stage could run tests, linter, and so forth and then create a wheel or similar artifact via setuptools. A second stage in the build can then only include a minimal set of dependencies to install and run the artifact (e.g. using python-slim as a base image).

5 years ago

Share CI steps between Docker and Travis

5 years ago

Add Dockerfile As per https://github.com/chakki-works/doccano/projects/2#card-16406087, this change adds a Dockerfile for the project. The Python distribution used by the image can be specified via a build-time argument. This enables us in the future to for example run the tests on a wide variety of Python versions. In the future, the Dockerfile could be extended to for example leverage multi-stage builds. In this case, the first stage could run tests, linter, and so forth and then create a wheel or similar artifact via setuptools. A second stage in the build can then only include a minimal set of dependencies to install and run the artifact (e.g. using python-slim as a base image).

5 years ago

*
!app/
app/staticfiles/
app/db.sqlite3
!data/
!tests/
!tools/
!requirements.txt