Storing Slicer application and extension packages is becoming an issue.
First, the midas server itself is not able to support a growing collection of item without sizing up the PHP memory on the server. See mailing list [1] and associated midas issue [2].
[1] http://slicer-devel.65872.n3.nabble.com/Extensions-server-maintenance-tp4031117.html
[2] See midasplatform/Midas#69
The over growing collection of packages require more storage and impacts the overall backup process associated the hosting server.
As discussed in [3], download statistics for both Slicer application and extension packages should be kept.
[3] http://slicer-devel.65872.n3.nabble.com/Extensions-server-maintenance-tp4031117p4031122.html
Problem 1
could be addressed ensuring issues like midasplatform/Midas#69 are addressed through the entire Midas stack.
Problem 2
could be addressed by removing the asset-store files associated with the packages. See below for more details.
The query referenced below will return asset-store paths associated with packages matching the following conditions:
-
the package is older than the last stable release '4.6.2'
-
the package is not release
-
asset-store paths do NOT match the one associated with package we want to keep
Generate list of asset-store file paths:
-
Shell script running Query_4: List asset-store paths associated with Slicer extension packages of interest.
-
Shell script running Query_5: List asset-store paths associated with Slicer application packages of interest.
Remove asset-store file paths:
- Python script will be used to process the text file obtained after running one of the query.
Note: In order to keep the download stats, the file should NOT be removed from the asset-store using either the Midas web interface or REST API. Instead, a shell script (or similar method) should be used.