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
Ports-mirror rummages around in Haikuports and makes backups of sources for our packages. It's handy, however used a considerable amount of locally bound resources and storage.
ports-mirror really needs refactored to use generic s3 buckets (aka Wasabi) for storage. This would enable us to archive large amounts of storage for cheap, while maintaining small and agile storage dependencies on our infrastructure
Ideas:
While archiving ports, store the date, time, source, sha256, recipe as metadata in s3
sha256 in metadata is important so we can compare what the recipe expects, and what is stored in s3.
We should be able to point haikuporter directly at the s3 storage provider ideally to reduce bandwidth within our infrastructure.
The text was updated successfully, but these errors were encountered:
Ports-mirror rummages around in Haikuports and makes backups of sources for our packages. It's handy, however used a considerable amount of locally bound resources and storage.
https://github.com/haiku/infrastructure/tree/master/containers/ports-mirror
ports-mirror really needs refactored to use generic s3 buckets (aka Wasabi) for storage. This would enable us to archive large amounts of storage for cheap, while maintaining small and agile storage dependencies on our infrastructure
Ideas:
The text was updated successfully, but these errors were encountered: