heckyel/mediagoblin
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Note how to run test suite under Docker.

Browse Source
This commit is contained in:
Ben Sturmfels 2020-04-14 18:40:55 +10:00
parent 912e5d2b41
commit cbd119168c
No known key found for this signature in database
GPG Key ID: 023C05E2C9C068F0
1 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
Dockerfile-debian-python3-sqlite
View File

@ -6,7 +6,7 @@
#
# To build this Docker image, run:
#
# docker build -t mediagoblin-python3 -f Dockerfile-debian-python3-sqlite # or
# docker build -t mediagoblin-python3 -f Dockerfile-debian-python3-sqlite . # or
# docker build -t mediagoblin-python3 - < Dockerfile-debian-python3-sqlite # with no build context
#
# The "- < Dockerfile" format advises Docker not to include the current
@ -22,12 +22,13 @@
#
# Then you can run the image with the upstream MediaGoblin code:
#
# docker run --interactive --tty --publish 6543:6543 mediagoblin-python
# docker run --interactive --tty --publish 6543:6543 mediagoblin-python3
#
# Or you can run with your local "mediagoblin" and "user_dev" directories
# bind-mounted into the container. This provides automatic code reloading and
# persistence:
#
# # TODO: Not working.
# docker run --interactive --tty --publish 6543:6543 --volume ./mediagoblin:/opt/mediagoblin/mediagoblin --volume ./extlib:/opt/mediagoblin/extlib mediagoblin-python3
#
# Alternatively you use docker-compose instead of separate build/run steps:
@ -36,6 +37,11 @@
# find mediagoblin user_dev -type d -exec chmod 775 {} \;
# find mediagoblin user_dev -type f -exec chmod 664 {} \;
# docker-compose up --build
#
# You can run the test suite with:
#
# docker run --tty mediagoblin-python3 bash -c "bin/python -m pytest ./mediagoblin/tests --boxed"
FROM debian:buster