doccano

Commit Graph

Author	SHA1	Message	Date
Hironsan	a3a054c393	Rename app dir to backend for pip installation	3 years ago
Johann Frei	419b863654	Add offline deployment to dockerignore	3 years ago
Hironsan	1c8ef0c654	Update docker-compose.prod.yml to remove frontend container	3 years ago
Hironsan	8f4fad340d	Change Dockerfile to use Pipfile	3 years ago
Hironsan	dfabe7c212	Add docker ignore path	3 years ago
Caroline Teicher	ff9978704d	Add linter for Dockerfile	5 years ago
Clemens Wolff	9206b499c2	Adopt nuxt folder structure	5 years ago
Clemens Wolff	3a26bbe8a0	Add code coverage	5 years ago
Clemens Wolff	07d5172b6c	Integrate webpack and django	5 years ago
Clemens Wolff	5e73682366	Remove auto-generated bundle files	5 years ago
Clemens Wolff	db1613a4bd	Add node_modules to ignore files	5 years ago
Clemens Wolff	3a2d2a73ac	Add flake8 linter to CI	5 years ago
Clemens Wolff	0b1f464c74	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
Clemens Wolff	c8e5f9b746	Share CI steps between Docker and Travis	5 years ago
Clemens Wolff	651e493c93	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

15 Commits (f8be085e020e721880a14682dbb042942a732efd)