[{"_1":2,"_165":-5,"_166":-5},"loaderData",{"_3":4,"_13":14,"_20":21,"_140":141},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","routes/_layout.r.$namespace.$reponame",{"_22":23,"_24":-5,"_25":11,"_26":11,"_27":28,"_29":30,"_31":-5,"_32":11,"_33":34,"_82":-5,"_83":84,"_133":-5,"_134":11,"_135":17,"_136":11,"_137":-5,"_138":139},"canonicalUrl","https://hub.docker.com/r/joshuaavalon/pypiserver/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","joshuaavalon","reponame","pypiserver","cloudBuildSource","isAutobuildsAvailable","repo",{"_35":36,"_37":38,"_40":41,"_42":30,"_43":11,"_44":45,"_46":47,"_48":49,"_51":30,"_27":28,"_52":53,"_54":39,"_55":56,"_57":58,"_59":60,"_61":-5,"_62":56,"_63":64,"_65":11,"_66":28,"_67":68,"_73":17,"_74":75,"_79":28,"_80":81},"categories",[],"content_types",[39],"image","date_registered","2018-07-29T07:03:13.393099Z","description","is_private","last_updated","2018-07-29T07:10:27.25362Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[50],"application/vnd.docker.container.image.v1+json","name","pull_count",278,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description",".. -*- mode: rst; coding: utf-8 -*-\n\n.. image:: pypiserver_logo.png\n :width: 300 px\n :align: center\n\n==============================================================================\npypiserver - minimal PyPI server for use with pip/easy_install\n==============================================================================\n|pypi-ver| |travis-status| |dependencies| |downloads-count| |python-ver| \\\n|proj-license|\n\n:Version: 1.2.2\n:Date: 2018-06-12 11:49:30\n:Source: https://github.com/pypiserver/pypiserver\n:PyPI: https://pypi.org/project/pypiserver/\n:Travis: https://travis-ci.org/pypiserver/pypiserver\n:Maintainers: Kostis Anagnostopoulos ,\n Matthew Planchard \n:License: zlib/libpng + MIT\n\n*pypiserver* is a minimal PyPI_ compatible server for *pip* or *easy_install*.\nIt is based on bottle_ and serves packages from regular directories.\nWheels, bdists, eggs and accompanying PGP-signatures can be uploaded\neither with *pip*, *setuptools*, `twine`_, `pypi-uploader`_, or simply copied\nwith *scp*.\n\n\n.. contents:: Table of Contents\n :backlinks: top\n\n\nQuickstart: Installation and Usage\n==================================\n*pypiserver* ``> 1.2.x`` works with python ``2.7`` and ``3.3+`` or *pypy*.\nOlder python-versions may still work, but they are not tested.\nFor legacy python versions, use ``pypiserver-1.1.x`` series.\n\n.. Tip::\n The commands below work on a unix-like operating system with a posix shell.\n The ``'~'`` character expands to user's home directory.\n\n If you're using Windows, you'll have to use their \"Windows counterparts\".\n The same is true for the rest of this documentation.\n\n\n1. Install *pypiserver* with this command::\n\n pip install pypiserver ## Or: pypiserver[passlib,watchdog]\n mkdir ~/packages ## Copy packages into this directory.\n\n See also `Alternative Installation methods`_.\n\n2. Copy some packages into your ``~/packages`` folder and then\n get your *pypiserver* up and running::\n\n pypi-server -p 8080 ~/packages & ## Will listen to all IPs.\n\n3. From the client computer, type this::\n\n ## Download and Install hosted packages.\n pip install --extra-index-url http://localhost:8080/simple/ ...\n\n # or\n pip install --extra-index-url http://localhost:8080\n\n ## Search hosted packages\n pip search --index http://localhost:8080 ...\n\n # Note that pip search does not currently work with the /simple endpoint\n\n See also `Client-side configurations`_ for avoiding tedious typing.\n\n4. Enter ``pypi-server -h`` in the cmd-line to print a detailed usage message::\n\n pypi-server [OPTIONS] [PACKAGES_DIRECTORY...]\n start PyPI compatible package server serving packages from\n PACKAGES_DIRECTORY. If PACKAGES_DIRECTORY is not given on the\n command line, it uses the default ~/packages. pypiserver scans this\n directory recursively for packages. It skips packages and\n directories starting with a dot. Multiple package directories can be\n specified.\n\n pypi-server understands the following options:\n\n -p, --port PORT\n listen on port PORT (default: 8080)\n\n -i, --interface INTERFACE\n listen on interface INTERFACE (default: 0.0.0.0, any interface)\n\n -a, --authenticate (UPDATE|download|list), ...\n comma-separated list of (case-insensitive) actions to authenticate\n Use '.' or '' for empty. Requires to have set the password (-P option).\n For example to password-protect package downloads (in addition to uploads)\n while leaving listings public, give:\n -P foo/htpasswd.txt -a update,download\n To drop all authentications, use:\n -P . -a .\n Note that when uploads are not protected, the `register` command\n is not necessary, but `~/.pypirc` still need username and password fields,\n even if bogus.\n By default, only 'update' is password-protected.\n\n -P, --passwords PASSWORD_FILE\n use apache htpasswd file PASSWORD_FILE to set usernames & passwords when\n authenticating certain actions (see -a option).\n If you want to allow un-authorized access, set this option and -a\n explicitly to empty (either '.' or'').\n\n --disable-fallback\n disable redirect to real PyPI index for packages not found in the\n local index\n\n --fallback-url FALLBACK_URL\n for packages not found in the local index, this URL will be used to\n redirect to (default: https://pypi.org/simple)\n\n --server METHOD\n use METHOD to run the server. Valid values include paste,\n cherrypy, twisted, gunicorn, gevent, wsgiref, auto. The\n default is to use \"auto\" which chooses one of paste, cherrypy,\n twisted or wsgiref.\n\n -r, --root PACKAGES_DIRECTORY\n [deprecated] serve packages from PACKAGES_DIRECTORY\n\n -o, --overwrite\n allow overwriting existing package files\n\n --hash-algo ALGO\n any `hashlib` available algo used as fragments on package links.\n Set one of (0, no, off, false) to disabled it. (default: md5)\n\n --welcome HTML_FILE\n uses the ASCII contents of HTML_FILE as welcome message response.\n\n -v\n enable INFO logging; repeat for more verbosity.\n\n --log-conf \n read logging configuration from FILE.\n By default, configuration is read from `log.conf` if found in server's dir.\n\n --log-file \n write logging info into this FILE.\n\n --log-frmt \n the logging format-string. (see `logging.LogRecord` class from standard python library)\n [Default: %(asctime)s|%(name)s|%(levelname)s|%(thread)d|%(message)s]\n\n --log-req-frmt FORMAT\n a format-string selecting Http-Request properties to log; set to '%s' to see them all.\n [Default: %(bottle.request)s]\n\n --log-res-frmt FORMAT\n a format-string selecting Http-Response properties to log; set to '%s' to see them all.\n [Default: %(status)s]\n\n --log-err-frmt FORMAT\n a format-string selecting Http-Error properties to log; set to '%s' to see them all.\n [Default: %(body)s: %(exception)s \\n%(traceback)s]\n\n pypi-server -h\n pypi-server --help\n show this help message\n\n pypi-server --version\n show pypi-server's version\n\n pypi-server -U [OPTIONS] [PACKAGES_DIRECTORY...]\n update packages in PACKAGES_DIRECTORY. This command searches\n pypi.org for updates and shows a pip command line which\n updates the package.\n\n The following additional options can be specified with -U:\n\n -x\n execute the pip commands instead of only showing them\n\n -d DOWNLOAD_DIRECTORY\n download package updates to this directory. The default is to use\n the directory which contains the latest version of the package to\n be updated.\n\n -u\n allow updating to unstable version (alpha, beta, rc, dev versions)\n\n Visit https://github.com/pypiserver/pypiserver for more information.\n\n\n\nClient-side Configurations\n==========================\nAlways specifying the the pypi url on the command line is a bit\ncumbersome. Since *pypiserver* redirects ``pip/easy_install`` to the\n``pypi.org`` index if it doesn't have a requested package, it's a\ngood idea to configure them to always use your local pypi index.\n\nConfiguring *pip*\n-----------------\nFor ``pip`` command this can be done by setting the environment variable\n``PIP_EXTRA_INDEX_URL`` in your ``.bashr/.profile/.zshrc``::\n\n export PIP_EXTRA_INDEX_URL=http://localhost:8080/simple/\n\nor by adding the following lines to ``~/.pip/pip.conf``::\n\n [global]\n extra-index-url = http://localhost:8080/simple/\n\n.. Note::\n If you have installed *pypiserver* on a remote url without *https*\n you wil receive an \"untrusted\" warning from *pip*, urging you to append\n the ``--trusted-host`` option. You can also include this option permanently\n in your configuration-files or environment variables.\n\n\nConfiguring *easy_install*\n--------------------------\nFor ``easy_install`` command you may set the following configuration in\n``~/.pydistutils.cfg``::\n\n [easy_install]\n index_url = http://localhost:8080/simple/\n\n\nUploading Packages Remotely\n===========================\nInstead of copying packages directly to the server's folder (i.e. with ``scp``),\nyou may use python tools for the task, e.g. ``python setup.py upload``.\nIn that case, *pypiserver* is responsible for authenticating the upload-requests.\n\n\n.. Note::\n We strongly advise to password-protected your uploads!\n\n It is possible to disable authentication for uploads (e.g. in intranets).\n To avoid lazy security decisions, read help for ``-P`` and ``-a`` options.\n\n\n*Apache*-like authentication (``htpasswd``)\n-------------------------------------------\n#. First make sure you have the *passlib* module installed (note that\n ``passlib>=1.6`` is required), which is needed for parsing the Apache\n *htpasswd* file specified by the ``-P``, ``--passwords`` option\n (see next steps)::\n\n pip install passlib\n\n#. Create the Apache *htpasswd* file with at least one user/password pair\n with this command (you'll be prompted for a password)::\n\n htpasswd -sc htpasswd.txt \n\n .. Tip:: Read this SO question for running `htpasswd` cmd\n under *Windows*:\n\n http://serverfault.com/questions/152950/how-to-create-and-edit-htaccess-and-htpasswd-locally-on-my-computer-and-then-u\n\n or if you have bogus passwords that you don't care because they are for\n an internal service (which is still \"bad\", from a security prespective...)\n you may use this public service:\n\n http://www.htaccesstools.com/htpasswd-generator/\n\n .. Tip:: When accessing pypiserver via the api, alternate authentication\n methods are available via the ``auther`` config flag. Any callable\n returning a boolean can be passed through to the pypiserver config in\n order to provide custom authentication. For example, to configure\n pypiserver to authenticate using the `python-pam`_::\n\n import pam\n pypiserver.default_config(auther=pam.authenticate)\n\n Please see `Using Ad-hoc authentication providers`_ for more information.\n\n#. You need to restart the server with the ``-P`` option only once\n (but user/password pairs can later be added or updated on the fly)::\n\n ./pypi-server -p 8080 -P htpasswd.txt ~/packages &\n\nUpload with *setuptools*\n------------------------\n#. On client-side, edit or create a ``~/.pypirc`` file with a similar content::\n\n [distutils]\n index-servers =\n pypi\n local\n\n [pypi]\n username:\n password:\n\n [local]\n repository: http://localhost:8080\n username: \n password: \n\n#. Then from within the directory of the python-project you wish to upload,\n issue this command::\n\n python setup.py sdist upload -r local\n\n\nUpload with `twine`_\n--------------------\nTo avoid storing you passwords on disk, in clear text, you may either:\n\n- use the ``register`` *setuptools*'s command with the ``-r`` option,\n like that::\n\n python setup.py sdist register -r local upload -r local\n\n- use `twine`_ library, which\n breaks the procedure in two steps. In addition, it supports signing\n your files with PGP-Signatures and uploading the generated `.asc` files\n to *pypiserver*::\n\n twine upload -r local --sign -identity user_name ./foo-1.zip\n\n\nUpload with `pypi-uploader`_\n----------------------------\nYou can also upload packages using `pypi-uploader`_, which\nobviates the need to download packages locally prior to uploading them to\npypiserver. You can install it with ``pip install pypi-uploader``, and\nassuming you have a ``pypi_local`` source set up in your ``~/.pypirc``,\nuse it like this::\n\n pypiupload packages mock==1.0.1 requests==2.2.1 -i pypi_local\n pypiupload requirements requirements.txt -i pypi_local\n\n\nAlternative Installation methods\n================================\nWhen trying the methods below, first use the following command to check whether\nprevious versions of *pypiserver* already exist, and (optionally) uninstall them::\n\n ## VERSION-CHECK: Fails if not installed.\n pypi-server --version\n\n ## UNINSTALL: Invoke again untill it fails.\n pip uninstall pypiserver\n\n\nInstalling the very latest version\n----------------------------------\nIn case the latest version in *pypi* is a pre-release, you have to use\n*pip*'s `--pre` option. And to update an existing installation combine it\nwith `--ignore-installed`::\n\n pip install pypiserver --pre -I\n\nYou can even install the latest *pypiserver* directly from *github* with the\nfollowing command, assuming you have *git* installed on your ``PATH``::\n\n pip install git+git://github.com/pypiserver/pypiserver.git\n\n\nInstalling it as standalone script\n----------------------------------\nThe git repository contains a ``pypi-server-standalone.py`` script,\nwhich is a single python file that can be executed without any other\ndependencies.\n\nRun the following commands to download the script with ``wget``::\n\n wget https://raw.github.com/pypiserver/pypiserver/standalone/pypi-server-standalone.py\n chmod +x pypi-server-standalone.py\n\nor with ``curl``::\n\n curl -O https://raw.github.com/pypiserver/pypiserver/standalone/pypi-server-standalone.py\n chmod +x pypi-server-standalone.py\n\nYou can then start-up the server with::\n\n ./pypi-server-standalone.py\n\nFeel free to rename the script and move it into your ``$PATH``.\n\n\nRunning on *heroku/dotcloud*\n----------------------------\nhttps://github.com/dexterous/pypiserver-on-the-cloud contains\ninstructions on how to run *pypiserver* on one of the supported cloud\nservice providers.\n\n\n\nRecipes\n=======\n\nManaging the package directory\n------------------------------\nThe ``pypi-server`` command has the ``-U`` option that searches for updates of\navailable packages. It scans the package directory for available\npackages and searches on pypi.org for updates. Without further\noptions ``pypi-server -U`` will just print a list of commands which must\nbe run in order to get the latest version of each package. Output\nlooks like::\n\n $ ./pypi-server -U\n checking 106 packages for newer version\n\n .........u.e...........e..u.............\n .....e..............................e...\n ..........................\n\n no releases found on pypi for PyXML, Pymacs, mercurial, setuptools\n\n # update raven from 1.4.3 to 1.4.4\n pip -q install --no-deps --extra-index-url https://pypi.org/simple -d /home/ralf/packages/mirror raven==1.4.4\n\n # update greenlet from 0.3.3 to 0.3.4\n pip -q install --no-deps --extra-index-url https://pypi.org/simple -d /home/ralf/packages/mirror greenlet==0.3.4\n\nIt first prints for each package a single character after checking the\navailable versions on pypi. A dot(`.`) means the package is up-to-date, ``'u'``\nmeans the package can be updated and ``'e'`` means the list of releases on\npypi is empty. After that it shows a *pip* command line which can be used\nto update a one package. Either copy and paste that or run\n``pypi-server -Ux`` in order to really execute those commands. You need\nto have *pip* installed for that to work however.\n\nSpecifying an additional ``-u`` option will also allow alpha, beta and\nrelease candidates to be downloaded. Without this option these\nreleases won't be considered.\n\n\nServing thousands of packages\n-----------------------------\n\nBy default, *pypiserver* scans the entire packages directory each time an\nincoming HTTP request occurs. This isn't a problem for a small number of\npackages, but causes noticeable slow-downs when serving thousands of packages.\n\nIf you run into this problem, significant speedups can be gained by enabling\npypiserver's directory caching functionality. The only requirement is to\ninstall the ``watchdog`` package, or it can be installed during ``pypiserver``\ninstallation, by specifying the ``cache`` extras option::\n\n pip install pypiserver[cache]\n\nIf you are using a static webserver such as *Apache* or *nginx* as\na reverse-proxy for pypiserver, additional speedup can be gained by\ndirectly serving the packages directory:\n\nFor instance, in *nginx* you may adding the following config to serve\npackages-directly directly (take care not to expose \"sensitive\" files)::\n\n location /packages/ {\n root /path/to/packages/parentdir;\n }\n\nIf you have packages that are very large, you may find it helpful to\ndisable hashing of files (set ``--hash-algo=off``, or ``hash_algo=None`` when\nusing wsgi).\n\n\nManaging Automated Startup\n--------------------------\nThere are a variety of options for handling the automated starting of\npypiserver upon system startup. Two of the most common are *systemd* and\n*supervisor*.\n\n\nRunning as a *systemd* service\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n*systemd* is installed by default on most modern Linux systems and as such,\nit is an excellent option for managing the pypiserver process. An example\nconfig file for ``systemd`` can be seen below::\n\n [Unit]\n Description=A minimal PyPI server for use with pip/easy_install.\n After=network.target\n\n [Service]\n Type=simple\n # systemd requires absolute path here too.\n PIDFile=/var/run/pypiserver.pid\n User=www-data\n Group=www-data\n\n ExecStart=/usr/local/bin/pypi-server -p 8080 -a update,download --log-file /var/log/pypiserver.log -P /etc/nginx/.htpasswd /var/www/pypi\n ExecStop=/bin/kill -TERM $MAINPID\n ExecReload=/bin/kill -HUP $MAINPID\n Restart=always\n\n WorkingDirectory=/var/www/pypi\n\n TimeoutStartSec=3\n RestartSec=5\n\n [Install]\n WantedBy=multi-user.target\n\nAdjusting the paths and adding this file as ``pypiserver.service`` into your\n``systemd/system`` directory will allow management of the pypiserver process with\n``systemctl``, e.g. ``systemctl start pypiserver``.\n\nMore useful information about *systemd* can be found at\nhttps://www.digitalocean.com/community/tutorials/how-to-use-systemctl-to-manage-systemd-services-and-units\n\n\nLaunching through *supervisor*\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\n`supervisor `_ has the benefit of being a pure python\npackage and as such, it provides excellent cross-platform support for process\nmanagement. An example configuration file for ``supervisor`` is given below::\n\n [program:pypi]\n command=/home/pypi/pypi-venv/bin/pypi-server -p 7001 -P /home/pypi/.htaccess /home/pypi/packages\n directory=/home/pypi\n user=pypi\n autostart=true\n autorestart=true\n stderr_logfile=/var/log/pypiserver.err.log\n stdout_logfile=/var/log/pypiserver.out.log\n\nFrom there, the process can be managed via ``supervisord`` using ``supervisorctl``.\n\n\nUsing a different WSGI-server\n-----------------------------\n- The *bottle* web-server which supports many WSGI-servers, among others,\n *paste*, *cherrypy*, *twisted* and *wsgiref* (part of python); you select\n them using the ``--server`` flag.\n\n- You may view all supported WSGI servers using the following interactive code::\n\n >>> from pypiserver import bottle\n >>> list(bottle.server_names.keys())\n ['cgi', 'gunicorn', 'cherrypy', 'eventlet', 'tornado', 'geventSocketIO',\n 'rocket', 'diesel', 'twisted', 'wsgiref', 'fapws3', 'bjoern', 'gevent',\n 'meinheld', 'auto', 'aiohttp', 'flup', 'gae', 'paste', 'waitress']\n\n- If none of the above servers matches your needs, invoke just the\n ``pypiserver:app()`` method which returns the internal WSGI-app WITHOUT\n starting-up a server - you may then send it to any WSGI-server you like.\n Read also the `Utilizing the API`_ section.\n\n- Some examples are given below - you may find more details in `bottle\n site `_.\n\nApache (*mod_wsgi*)\n~~~~~~~~~~~~~~~~~~~~~\nTo use your *Apache2* with *pypiserver*, prefer to utilize *mod_wsgi* as\nexplained in `bottle's documentation `_.\n\n.. Note::\n If you choose instead to go with *mod_proxy*, mind that you may bump into problems\n with the prefix-path (see `#155 `_).\n\n1. Adapt and place the following *Apache* configuration either into top-level scope,\n or inside some ```` (contributed by Thomas Waldmann)::\n\n WSGIScriptAlias / /yoursite/wsgi/pypiserver-wsgi.py\n WSGIDaemonProcess pypisrv user=pypisrv group=pypisrv umask=0007 \\\n processes=1 threads=5 maximum-requests=500 \\\n display-name=wsgi-pypisrv inactivity-timeout=300\n WSGIProcessGroup pypisrv\n WSGIPassAuthorization On ## (Optional) Use also apache's authentication.\n\n \n Require all granted\n \n\n or if using older ``Apache < 2.4``, substitute the last part with this::\n\n \n Order deny,allow\n Allow from all\n \n\n2. Then create the ``/yoursite/cfg/pypiserver.wsgi`` file and make sure that\n the ``user`` and ``group`` of the ``WSGIDaemonProcess`` directive\n (``pypisrv:pypisrv`` in the example) have the read permission on it::\n\n import pypiserver\n\n conf = pypiserver.default_config(\n root = \"/yoursite/packages\",\n password_file = \"/yoursite/htpasswd\", )\n application = pypiserver.app(**conf)\n\n\n .. Tip::\n If you have installed *pypiserver* in a virtualenv, follow ``mod_wsgi``'s\n `instructions `_\n and prepend the python code above with the following::\n\n import site\n\n site.addsitedir('/yoursite/venv/lib/pythonX.X/site-packages')\n\n.. Note::\n For security reasons, notice that the ``Directory`` directive grants access\n to a directory holding the *wsgi* start-up script, alone; nothing else.\n\n\ngunicorn\n~~~~~~~~\n\nThe following command uses *gunicorn* to start *pypiserver*::\n\n gunicorn -w4 'pypiserver:app(root=\"/home/ralf/packages\")'\n\nor when using multiple roots::\n\n gunicorn -w4 'pypiserver:app(root=[\"/home/ralf/packages\", \"/home/ralf/experimental\"])'\n\n\npaste/pastedeploy\n~~~~~~~~~~~~~~~~~\n`paste `_ allows to run multiple WSGI applications\nunder different URL paths. Therefore it's possible to serve different set\nof packages on different paths.\n\nThe following example ``paste.ini`` could be used to serve stable and\nunstable packages on different paths::\n\n [composite:main]\n use = egg:Paste#urlmap\n /unstable/ = unstable\n / = stable\n\n [app:stable]\n use = egg:pypiserver#main\n root = ~/stable-packages\n\n [app:unstable]\n use = egg:pypiserver#main\n root = ~/stable-packages\n ~/unstable-packages\n\n [server:main]\n use = egg:gunicorn#main\n host = 0.0.0.0\n port = 9000\n workers = 5\n accesslog = -\n\n.. Note::\n You need to install some more dependencies for this to work, like::\n\n pip install paste pastedeploy gunicorn pypiserver\n\n The server can then start with::\n\n gunicorn_paster paste.ini\n\n\nBehind a reverse proxy\n----------------------\nYou can run *pypiserver* behind a reverse proxy aswell.\n\nNginx\n~~~~~\nExtend your nginx configuration::\n\n upstream pypi {\n server pypiserver.example.com:12345 fail_timeout=0;\n }\n\n server {\n server_name myproxy.example.com;\n\n location / {\n proxy_set_header Host $host:$server_port;\n proxy_set_header X-Forwarded-Proto $scheme;\n proxy_set_header X-Real-IP $remote_addr;\n proxy_pass http://pypi;\n }\n }\n\n\nUtilizing the API\n-----------------\nIn order to enable ad-hoc authentication-providers or to use WSGI-servers\nnot supported by *bottle* out-of-the-box, you needed to launch *pypiserver*\nvia its API.\n\n- The main entry-point for configuring *pypiserver* is the `pypiserver:app()\n `_\n function. This function returns the internal WSGI-app that you my then\n send to any WSGI-server you like.\n\n- To get all ``pypiserver:app()`` keywords and their explanations, read the\n function `pypiserver:default_config()\n `_.\n\n- Finally, to fire-up a WSGI-server with the configured app, invoke\n the ``bottle:run(app, host, port, server)`` function.\n Note that *pypiserver* ships with it's own copy of *bottle*; to use it,\n import it like that: ``from pypiserver import bottle``\n\nUsing ad-hoc authentication providers\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\nThe ``auther`` keyword of ``pypiserver:app()`` function maybe set only using\nthe API. This can be any callable that returns a boolean when passed\nthe *username* and t","has_starred","hub_user","immutable_tags_settings",{"_69":11,"_70":71},"enabled","rules",[72],".*","is_automated","permissions",{"_76":17,"_77":11,"_78":11},"read","write","admin","user","storage_size",388880375,"orgData","recentTags",[85,123],{"_86":39,"_87":88,"_89":90,"_91":92,"_93":94,"_44":112,"_113":88,"_114":28,"_115":50,"_51":116,"_117":118,"_119":103,"_120":112,"_121":60,"_122":17},"content_type","creator",2167072,"full_size",32527478,"id",31951343,"images",[95],{"_96":97,"_98":99,"_100":101,"_102":103,"_104":105,"_106":107,"_108":101,"_109":-5,"_110":90,"_57":60,"_111":-5},"architecture","amd64","digest","sha256:de896cbad29e78bf54a591739ff0d460b6b34b1f7f6328b7823dcd584cbe300b","features","","last_pulled","2026-09-11T09:34:00.023536494Z","last_pushed","2018-07-29T07:04:36Z","os","linux","os_features","os_version","size","variant","2018-07-29T07:04:35.208167Z","last_updater","last_updater_username","media_type","latest","repository",5799441,"tag_last_pulled","tag_last_pushed","tag_status","v2",{"_86":39,"_87":88,"_89":124,"_91":125,"_93":126,"_44":131,"_113":88,"_114":28,"_115":50,"_51":132,"_117":118,"_119":129,"_120":131,"_121":60,"_122":17},356331359,31951437,[127],{"_96":97,"_98":128,"_100":101,"_102":129,"_104":130,"_106":107,"_108":101,"_109":-5,"_110":124,"_57":60,"_111":-5},"sha256:d35627e7f879b87c17efa19cbccea377decf0ab92e27f3f1f1048bb29b24c5a0","2026-09-11T09:30:33.037741776Z","2018-07-29T07:10:27Z","2018-07-29T07:10:26.916175Z","v1.2.2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_33":142,"_149":150,"_138":163,"_164":11},{"_35":143,"_37":144,"_40":41,"_42":30,"_43":11,"_44":45,"_46":47,"_48":145,"_51":30,"_27":28,"_52":53,"_54":39,"_55":56,"_57":58,"_59":60,"_61":-5,"_62":56,"_63":64,"_65":11,"_66":28,"_67":146,"_73":17,"_74":148,"_79":28,"_80":81},[],[39],[50],{"_69":11,"_70":147},[72],{"_76":17,"_77":11,"_78":11},"tags",{"_151":152,"_153":-5,"_154":-5,"_155":156},"count",2,"next","previous","results",[157,160],{"_86":39,"_87":88,"_89":124,"_91":125,"_93":158,"_44":131,"_113":88,"_114":28,"_115":50,"_51":132,"_117":118,"_119":129,"_120":131,"_121":60,"_122":17},[159],{"_96":97,"_98":128,"_100":101,"_102":129,"_104":130,"_106":107,"_108":101,"_109":-5,"_110":124,"_57":60,"_111":-5},{"_86":39,"_87":88,"_89":90,"_91":92,"_93":161,"_44":112,"_113":88,"_114":28,"_115":50,"_51":116,"_117":118,"_119":103,"_120":112,"_121":60,"_122":17},[162],{"_96":97,"_98":99,"_100":101,"_102":103,"_104":105,"_106":107,"_108":101,"_109":-5,"_110":90,"_57":60,"_111":-5},[],"canDeleteTags","actionData","errors"]

joshuaavalon/pypiserver

Tags for joshuaavalon/pypiserver