You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
S3-compatible object storage β a MinIO fork maintained by PGSTY
PGSTY SILO is a MinIO fork maintained by PGSTY Provide packages, images, console, and CVE fixes
Why should this be added?
Minio compatible S3 object storage with docs how to migrate from dead minio to Silo
AGPL 3 license
Restored and improved WebUI
S3-compatible cli client
Silo manifest with assurance not to change license or make any pay/login wall Manifest
The root password is generated at install and stored as MINIO_ROOT_PASSWORD in /etc/default/silo. Use it to log into the console on port 9001, then create dedicated access keys for your S3 clients.
Two ports: 9000 serves the S3 API, 9001 the web console. Object data lives in /opt/silo_data - back that up, or better, give the container a dedicated disk and point MINIO_VOLUMES at it.
Coming from MinIO? Silo reads the same data directory and MINIO_* settings. See https://silo.pgsty.com/compatibility/migration/ before moving an existing deployment.
Note: This is not in the official repo yetβit's just a dev version! After merging into ProxmoxVE, it will need to be recreated.
1 - Test installation ( Default install ) - PASS
2 - Test Web UI ( If applicable ) - PASS
3 - Test account Creation and login ( If applicable ) - PASS
4 - Test basic app features. - PASS (tested basic bucket creation and file upload)
5 - Check update function with following commands: - PASS
Activity
github-actions commentedon Sep 27, 2026
The SIlo script is ready for testing:
Default credentials:
Username: silo-admin
The root password is generated at install and stored as MINIO_ROOT_PASSWORD in /etc/default/silo. Use it to log into the console on port 9001, then create dedicated access keys for your S3 clients.
Two ports: 9000 serves the S3 API, 9001 the web console. Object data lives in /opt/silo_data - back that up, or better, give the container a dedicated disk and point MINIO_VOLUMES at it.
Coming from MinIO? Silo reads the same data directory and MINIO_* settings. See https://silo.pgsty.com/compatibility/migration/ before moving an existing deployment.
Note: This is not in the official repo yetβit's just a dev version! After merging into ProxmoxVE, it will need to be recreated.
Discord testing thread: https://discord.com/channels/1302816934508630047/1553696405259026553
cxmorgan commentedon Sep 27, 2026
1 - Test installation ( Default install ) - PASS
2 - Test Web UI ( If applicable ) - PASS
3 - Test account Creation and login ( If applicable ) - PASS
4 - Test basic app features. - PASS (tested basic bucket creation and file upload)
5 - Check update function with following commands: - PASS
ill try deeper inspection in nearest future
github-actions commentedon Sep 30, 2026
A PR has been created for silo: community-scripts/ProxmoxVE#17614
MickLesk commentedon Sep 30, 2026
Merged with #17614 in ProxmoxVE
github-actions commentedon Sep 30, 2026
Files deleted with PR #2340