...
- A write-up on which github.txt Python packages could move to a package cache, and which could be handled via other means is written up in
Jira Legacy server System JIRA serverId 13fd1930-5608-3aac-a5dd-21b934d3a4b4 key PLAT-1907 - Notes on setting up Artifactory and some timing / test run information is here
- Notes on setting up DevPI and timing results are here
DevPI vs. Artifactory
| DevPI | Artifactory | |
|---|---|---|
| Cost | OSS (MIT license) | OSS version seems not to support PyPI? Probably in the $50 - $100 month range based on competitor costs |
| Devstack local cache? | Yes | Probably not due to licensing |
| Speed | Test times were slightly faster in DevPI, probably more to do with it being on the host machine instead of Docker more than the package itself. They are likely comparable speed-wise. | |
| UI | Web, did not try. | Full featured, easy to browse packages, user permissions, etc |
| Command line | Full featured | Seems pretty limited to pip functionality, did not dig into it though |
| Ease of Setup | Easy for a local setup | Easy for a local setup |
| High Availability / Global cache | Provides single-writer, multiple-reader replication functionality, seems pretty new but probably robust enough for our use cases. Designed for geographically distributed systems, so we could place servers in different locations. | Provides localized cluster functionality. Requires Enterprise licensing. All servers need to be on the same LAN and share the same database server. |
| Database | sqlite3 | MySQL, Oracle, MS SQL, PostgreSQL |
| Filesystem | local, PostgreSQL (pls no), other plugins? | local (synchronizable in HA configuration), S3, NFS |