I have a question about maintenance of devpi. It seems like if used longer
term, it has a couple of point that need to be addressed one way or another:
1. Constantly growing number of cached pypi files.
2. Constantly growing size of sqlite database.
Are there any ways to manage amount of disk space required in both cases?
How do people usually deal with this? By increasing disk space, maybe fully
Mintel Group Ltd | 11 Pilgrim Street | London | EC4V 6RN
Registered in England: Number 1475918. | VAT Number: GB 232 9342 72
Contact details for our other offices can be found at
This email and any attachments may include content that is confidential,
or otherwise protected under applicable law. Unauthorised disclosure,
or use of the contents is prohibited and may be unlawful. If you have
received this email in error,
including without appropriate authorisation, then please reply to the
sender about the error
and delete this email and any attachments.
We maintain a devpi infrastructure (one master + several globally distributed replicas) and are facing a scheduled outage of our master server due to external conditions.
Devpi version info:
We will be able to shut down our master in a controlled manner and duration of outage is expected to be less then 5 mins. Also configuration of master (ip, dns, ...) will not change.
Given that I'm no very deep into devpi, I have a couple of questions/assumptions regarding impact and system behaviour, which I'd like to get your input on:
While the master is down, I'd assume the following operations to fail:
* devpi login to replica
* devpi upload (with/without docs) to replica
While master is down, I'd assume the following operations to work:
* pip install -i URL_TO_REPLICA/user/index
* browser access to indices/release files/docu via URL_TO_REPLICA/user/index
Are these assumptions correct?
After booting our master successfully, would any manual interaction be required to ensure previously (before master shutdown) operational state?