Hello,
Is it possible to automate the updating of private repositories on the wapt-get server?
For example: I import the Firefox 40.0.3-20 repository, and the wapt-get server regularly checks if a new Firefox repository exists and automatically updates it in the various groups.
Best regards
Updating the repositories on the server
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 :
One technique I know is to directly activate a second WAPT repository in your clients and replicate this second repository locally.
I've tried, with great difficulty, to explain this here:
http://wiki.lesfourmisduweb.org/index.p ... -Repo_Wapt
http://wiki.lesfourmisduweb.org/index.p ... ts_distant
But if I may, I don't recommend automating this procedure, as you risk waking up one morning to find your computer network with Firefox not working because it wasn't tested.
WAPT is very convenient and saves time, but human verification of new software on our network seems essential.
Simon
I've tried, with great difficulty, to explain this here:
http://wiki.lesfourmisduweb.org/index.p ... -Repo_Wapt
http://wiki.lesfourmisduweb.org/index.p ... ts_distant
But if I may, I don't recommend automating this procedure, as you risk waking up one morning to find your computer network with Firefox not working because it wasn't tested.
WAPT is very convenient and saves time, but human verification of new software on our network seems essential.
Simon
-
angelshurikan
- Messages: 9
- Registration: Sep 22, 2015 - 08:47
Thanks for your reply.
Basically, the idea is to have two PCs: a Wapt-Get server and a TIS client.
Steps:
1. The TIS client updates.
2. Retrieves the *.wapt files from the server.
3. Modifies the repositories to make them compatible with the Wapt-Get server.
Good idea. Otherwise, I prefer the rsync method to synthesizing because synthesizing is bidirectional, while this is unidirectional, and it allows you to execute your script after the synchronization.
As soon as I have time, I'll test this method.
Thanks again.
Basically, the idea is to have two PCs: a Wapt-Get server and a TIS client.
Steps:
1. The TIS client updates.
2. Retrieves the *.wapt files from the server.
3. Modifies the repositories to make them compatible with the Wapt-Get server.
Good idea. Otherwise, I prefer the rsync method to synthesizing because synthesizing is bidirectional, while this is unidirectional, and it allows you to execute your script after the synchronization.
As soon as I have time, I'll test this method.
Thanks again.
