Page 1 of 1
Updating the repositories on the server
Published: Dec 9, 2015 - 8:45 PM
by angelshurikan
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
Re: Updating repositories on the server
Published: Dec 10, 2015 - 09:21
by sfonteneau
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
Re: Updating repositories on the server
Published: Dec 17, 2015 - 08:49
by angelshurikan
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.