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. |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| README.rst | ||
| bumpver.py | ||
| check_readme.sh | ||
| commit-standalone.sh | ||
| gen-standalone.sh | ||
| package.sh | ||
| pypiserver-1.2.6-py2.py3-none-any.whl | ||
| test-docker.sh | ||
| test.htpasswd | ||
| test_standalone.sh | ||
README.rst
==================== Build scripts folder ==================== Files: ====== - ``bumpver.py`` : Bump, commit and tag new project versions - ``check_readme.sh`` : Check that README has no RsT-syntactic errors. - ``commit-standalone.sh`` : Create an executable file and add it into `standalone` branch. - ``gen-standalone.sh`` : Invoked by `commit-standalone.sh`. - ``git-new-workdir`` : Invoked by `gen-standalone.sh`. - ``package.sh`` : Build deployable artifact (wheel) in ``/dist/`` folder. - ``README.rst`` : This file. Release check-list: =================== 1. Update ``/CHANGES.rst`` (+ Title + Date) & ``/README.rst``. 2. Push to GitHub to run all TCs once more. 3. Bump version: commit & tag it with ``/bin/bumpver.py``. Use ``--help``. Read `PEP-440 <https://www.python.org/dev/peps/pep-0440/`_ to decide the version. 4. Push it in GitHub with ``--follow-tags``. 5. Generate package *wheel* with ``/bin/package.sh``. 6. Upload to PyPi with ``twine upload -s -i <gpg-user> dist/*``: 7. Run ``bin/commit-standalone.sh``. 7. Ensure that the new tag is built on hub.docker.com as ``latest`` and as a direct tag reference. 8. Copy release notes from ``/CHANGES.rst`` in GitHub as new *"release"* page on the new tag. Check syntactic differences between ``.md`` and ``.rst`` files.