Page 1 of 1

[RESOLVED] Secondary repository synchronization rules

Published: June 12, 2024 - 10:25
by tcaliste
Hello,

I have a question regarding the secondary repository synchronization feature.
How can we limit storage usage at each of our industrial sites while still being able to select/assign packages from the private repository to different secondary repositories?
Currently, I don't see a way to synchronize only a portion of the private repository for each site.
Does a secondary repository selection system exist for WAPT packages/OS deployments, etc.?
Is this feature under development? If so, do you have any idea of ​​the target version for its integration?

Thank you for your answers.

Best regards.

Re: Secondary repository synchronization rules

Published: June 12, 2024 - 2:31 PM
by dcardon
Hi Théo,

the differentiated secondary repository feature (which only synchronizes what the site needs) is currently under development.

Improving the management of remote sites is one of our current priorities. For small sites without secondary repositories, we are integrating the "peercache" feature into the WAPT agent, which allows two machines to share the packages they have downloaded. Peercache is in alpha version internally, and we hope to have it in the next WAPT version, 2.6 or 2.7.

The "proxycache" feature (differentiated repository) will be the next step.

Best regards,

Denis