Hello everyone,
I have a quick question: is it possible to prevent a repository from synchronizing a specific package?
For context, I have my WAPT server with several packages and four repositories (A, B, C, D) on different clients.
However, some large packages, like Office 365, are only usable by two clients using repositories A and B. The clients using repositories C and D will never need this package, but they synchronize it anyway, which consumes space on their servers (yes, I have very little).
So, my question is: can I tell repositories C and D to synchronize all packages from the main server except for the 32-bit Office package?
WAPT Server version: 2.6.0.17392 Ubuntu 20.04
WAPT Agent version: 2.6.0.17392
restrict the synchronization of certain packages on a repository
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Hi Augustin,
Currently, this isn't possible (except by using a synchronization system other than WAPT, such as rsync, where certain files are excluded).
We're currently considering replacing the current synchronization of secondary repositories with on-demand synchronization when the file is requested (essentially a peercache in server mode, which only downloads on demand). However, this mode isn't available yet.
Currently, this isn't possible (except by using a synchronization system other than WAPT, such as rsync, where certain files are excluded).
We're currently considering replacing the current synchronization of secondary repositories with on-demand synchronization when the file is requested (essentially a peercache in server mode, which only downloads on demand). However, this mode isn't available yet.
Hello Simon,
thanks for the feedback.
For now, I'll leave it as is, but yes, I'm really looking forward to on-demand synchronization being implemented.
I still have some Windows 10 machines and some brand new, fully Windows 11 fleets, and since the updates are fully synchronized, Windows 10 updates are synchronized to repositories of clients running full Windows 11.
Have a good weekend.
thanks for the feedback.
For now, I'll leave it as is, but yes, I'm really looking forward to on-demand synchronization being implemented.
I still have some Windows 10 machines and some brand new, fully Windows 11 fleets, and since the updates are fully synchronized, Windows 10 updates are synchronized to repositories of clients running full Windows 11.
Have a good weekend.
