* chore: convert bin/README to md
* feat: replace all dates with bumpver
* chore: date in README is now changed by `bumpver`
* chore: clarify the RC workflow
* chore: use global `/tmp` in RC
* chore: slightly prettier description
* chore: move changes file to env
* chore: introduce release_tag workflow
chore(wip): test trigger on PR
chore(wip): add filtered diff
chore(wip): switch to PATTERNS
chore(wip): up to bumpver
chore(wip): temporary disable check
chore(wip): setup python
chore(wip): test with a specific version
chore(wip): test bumpver commit
chore(wip): fix the bumpver usage
chore: cleanup the release_tag workflow
* chore: create draft release from CI
* chore: update the docs
* chore: provide details on the release process
* chore: tiny header update
* chore: remove commented-out code
* feat: dependabot
- add dependabot yml file to look in the docker & requirements folders
- split the requirements out of the test.pip into a test-requirements.pip file so dependabot recognizes it
It was found that in order to have the python dependabot
recognize the requirements a naming convention had to be
followed
* feat: dependabot
alter to monthly
* feat: markdown diff
Add a conditional check to output a diff between
what mdformat expects and what is actually in the
README.
* feat: markdown conversion
logo and badges
* feat: markdown conversion
fix logo path
* feat: markdown
table changes
* feat: markdown
table alignment
* feat: markdown
check toc
* feat: markdown
toc additions
* feat: markdown
quickstart section
* feat: dependabot
more details section in quick start
* feat: dependabot
correct bold
* feat: markdown
client side config, pip
* feat: markdown
typo in title
* feat: markdown
typo in configuring pip
* feat: markdown
apache like authentication section
an initial cut to view the markdown
in github
* feat: markdown
typo in markdown link
* feat: markdown
remove trailing colon
* feat: markdown
typo in shell markdown
* feat: markdown
standardize on 4 space indent in shell code block
* feat: markdown
complete markdown for section up to alternate installation methods
* feat: markdown
add more of the contents to test with
* feat: markdown
contents
* feat: markdown
contents
* feat: markdown
contents
* feat: markdown
dquote>
dquote> recipes
* feat: markdown
dquote>
dquote> recipes
* feat: markdown
dquote>
dquote> up to licensing
* feat: markdown
dquote>
dquote> contents
* Update README.md
Missing exclamation mark
* Update README.md
missing link
* Update README.md
remove duplicated text
* Update README.md
bold differences it Table of contents
* Update README.md
additional bold changes in table of contents
* Update README.md
broken link
* Update README.md
typo in link fix
* Update README.md
change code block to text as shell highlighting was showing some items in red
* Update README.md
code block shell to text
* Update README.md
correct pypi-server update section
* feat: markdown
dquote>
dquote> link back to TOC title
* Update README.md
change link to TOC title
* Update README.md
link test
* Update README.md
link update
* Update README.md
link update
* Update README.md
link update
* feat: markdown
links
* Update README.md
change the level of indent for uploading packages remotely
* Update README.md
add link to python-pam
* feat: markdown
apache link to TOC not working.
* Update README.md
grammar
* Update README.md
typo bold
* feat: markdown
undo bolded text in TOC and titles as linking does
not work
* feat: markdown
remove bold from TOC
* feat: feature
more link issues
* feat: markdown
fixing broken links
* feat: markdown
change text slightly as markdown only links to plain text
* feat: markdown
typo
* feat: markdown
more link typos
* Update README.md
typo in link
* Update README.md
link will not work with braces in the titles
* feat: markdown
run mdformat and apply changes, :) lint!
* feat: markdown
- check via mdformat
- remove old check script
- update test-requirements.txt
* feat: markdown
correct the errors in the mdformat run command
* feat: markdown
for testing remove all the actual jobs
* feat: markdown
re-run mdformat
* feat: markdown
put the jobs back in after testing the mdformat
cmd for passing and failing via workflow dispatch
* feat: markdown
remove references to README.md
* feat: markdown
change action to workflow dispatch for testing
* feat: markdown
- update docker igore
- alter unit test to look for version number after md changes
* feat: markdown
black linting
* feat: markdown
update comments
* feat: markdown
update bumpver to look at md rather than rst file
* feat: markdown
replace workflow dispatch with pull request
to get ready for the final PR
* feat: markdown-delete-original
delete the original rst file
* feat: markdown-delete-original
change ci to workflow dispatch for testing
* feat: markdown-delete-original
revert workflow dispatch
* feat: markdown-badge-links
set the links back to the original
URLs.
* feat: markdown-badge-links
fix brackets
* feat: markdown
update the version and date
* feat: markdown conversion
markdown changes to conform to mdformat tooling.
* feat: dependabot
- add dependabot yml file to look in the docker & requirements folders
- split the requirements out of the test.pip into a test-requirements.pip file so dependabot recognizes it
It was found that in order to have the python dependabot
recognize the requirements a naming convention had to be
followed
* feat: dependabot
alter to monthly
* fix: run on push only on master, otherwise only in PRs
* fix: pin versions
* chore: print python version
* chore: print python version
* chore: force upgrade setuptools & remove version prints
* Basic attempt for a release workflow in GH Actions
* move docker release to `release.yml`
* return the docker steps to ci.yml
* return the deploy-docker step to release.yml
* add wait for tests GA
Adds a new helper script to determine which docker tags are needed for a
given ref going through CI, and uses those tags to populate the GH
actions matrix for a docker deploy step.
* Docker improvements
This addresses much of what was brought up in #359. Specifically, it:
- Significantly improves testing for the Docker image, adding a
`docker/test_docker.py` file using the regular pytest machinery to
set up and run docker images for testing
- Hopefully addresses a variety of permissions issues, by being explicit
about what access pypiserver needs and asking for it, only erroring
if that access is not available
- Requires RX permissions on `/data` (R to read files, X to list files
and to be able to cd into the directory. This is important since
`/data` is the `WORKDIR`)
- Requires RWX permissions on `/data/packages`, so that we can list
packages, write packages, and read packages.
- When running in the default configuration (as root on Linux or
as the pypiserver-named rootish user on Mac), with no volumes
mounted, these requirements are all satisfied
- Volume mounts still must be readable by the pypiserver user (UID
9898) in order for the container to run. However, we now error early
if this is not the case, and direct users to a useful issue.
- If the container is run as a non-root, non-pypiserver user (e.g.
because someone ran `docker run --user=<user_id>`, we try to run
pypiserver as that user). Provided that user has access to the
necessary directories, it should run fine.
- Fixes issues with running help and similar commands
- Updates the Docker image to use `PYPISERVER_PORT` for port
specification, while still falling back to `PORT` for backwards
compatibility
- Moves some docker-related things into a `/docker` directory
- Adds a `Makefile` for building a test fixture package sdist and wheel,
so that test code can call `make mypkg` and not need to worry about it
potentially building multiple times
The only issue #359 raises that's not addressed here is the one of
running pypiserver in the Docker container using some non-default server
for performance. I would like to do some benchmarking before deciding on
what to do there.
Adds an aggregate "tests" job to CI so that we can gate merges on that
without needing to keep merge gates up-to-date with the names of the
various jobs that collectively represent "all tests".
Also dropped the `pull-request` trigger, which I included originally
because I wasn't sure whether the tests on push would run for forks,
which they do!
* Switch to GH actions
Removes the travis config and adds a GH actions config. Resolves#360.
As part of this:
- only runs the README check once, instead of for each python version
- only runs mypy once, removing it from tox
- unifies the pypy and cpython tests in tox by separating dev and test
requirements, and only installing the latter for running tests in tox
* Update README w/badge & link to GH actions tests
