Hello,
Is it possible to prevent a package from being cached on the client PC, and
instead only have the script executed there? I have several large packages (the largest is 6 GB) and I'd like to link them to certain PCs that already have the software installed (before the WAPT agent was set up). Therefore, I'd like to avoid the WAPT agent downloading all the packages from the server, then running the script, and simply detecting that the software is already installed. If I'm not mistaken, the package is first downloaded to the client PC (as a .WAPT file) and then decompressed. This means that 12 GB of free space is wasted in the end. And I think some of our client PCs don't have that much free space on their hard drives.
Is there a solution to get around this problem?
Best regards,
Christophe.
Do not cache a package
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
-
dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello Christophe0110,
This can be convenient, but you have to keep in mind the limitations of this type of operation, which are that the dependency is not clearly displayed (in the control file), and that consequently, you have to be sure that there will still be a network when the package is installed, because it will not have been cached beforehand (because waptagent cannot anticipate that it will need it).
Sincerely,
Denis Cardon
For large packages like this one, it's possible to separate the data file from the configuration package. In your configuration package, you can check if the software is already installed, and if not, force the installation from within setup.py using WAPT.install('xxx-mypackage').Christophe0110 wrote: ↑Jul 18, 2019 - 3:08 PM Is it possible to prevent a package from being cached on the client PC, and instead have the script executed on it?
I have several large packages (6 GB for the largest) and I'd like to link them to certain PCs that already have the software installed (before the WAPT agent was set up). Therefore, I'd like to avoid the WAPT agent downloading all the packages from the server, then running the script, and simply detecting that the software is already installed. If I'm not mistaken, the package is first downloaded to the client PC (as a .WAPT file) and then decompressed. This means that 12 GB of free space is wasted in the end. And I think some of our client PCs don't have that much free space on their hard drives.
Is there a solution to get around this problem?
This can be convenient, but you have to keep in mind the limitations of this type of operation, which are that the dependency is not clearly displayed (in the control file), and that consequently, you have to be sure that there will still be a network when the package is installed, because it will not have been cached beforehand (because waptagent cannot anticipate that it will need it).
Sincerely,
Denis Cardon
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
