forked from github.com/pypiserver
d162d660c4
Thanks for your PR! I was wondering why everyone kept complaining about `bcrypt`, when my local tests were succeeding just fine, so I spent some time making the docker test script replicate the error. Turns out the `.htpasswd` files I was generating were using md5, so they were not triggering the error. The htpasswd file in this update does use bcrypt encryption, so it triggers a 500 error on the previous version of the Dockerfile. I also updated the test to be a bit more thorough, validating an authenticated upload in addition to just making sure the server is running. The only other change I made was to move `requirements.txt` into a more specific `docker-requirements.txt` file, just to make it clear that its intention is to be a part of the docker build and not the normal install process.
25 lines
316 B
YAML
25 lines
316 B
YAML
sudo: required
|
|
language: python
|
|
services: docker
|
|
|
|
python:
|
|
- 2.7
|
|
- 3.4
|
|
- 3.5
|
|
- 3.6
|
|
- pypy
|
|
- pypy3
|
|
|
|
install:
|
|
- pip install -U setuptools twine pip sphinx tox tox-travis
|
|
|
|
script:
|
|
- ./bin/test-docker.sh
|
|
- ./bin/test_standalone.sh
|
|
- tox
|
|
- ./bin/check_readme.sh
|
|
|
|
branches:
|
|
except:
|
|
- standalone
|