Tranquil IT Forum

Hello,
I'm currently considering setting up a public repository. Do you have any documentation or recommendations for setting it up in version 1.6 (nginx)?
https://wiki.lesfourmisduweb.org/index. ... apt_public
Thank you

James wrote: ↑Oct 12, 2018 - 1:59 PM Hello,
I'm currently considering setting up a public repository. Do you have any documentation or recommendations for setting it up in version 1.6 (nginx)?
https://wiki.lesfourmisduweb.org/index. ... apt_public
Thank you

My document is completely outdated. It should be forgotten

Do you want to make your current Wapt server available or do something else?

The idea is to install a WAPT server that will act solely as a centralized repository (I update packages via TIS or make specific developments available there), accessible via the web. Technicians at the different sites configure this repository on their WAPT servers and import packages manually.
Perhaps a second option could be considered to synchronize the central repository across the different sites.
Thank you.

Good evening James,

James wrote: ↑Oct 15, 2018 - 10:43 The idea is to install a WAPT server that will act solely as a centralized repository (I update packages via TIS or make specific developments available on it), accessible via the web. Technicians at the different sites configure this repository on their WAPT servers and import the packages manually.

A WAPT public repository (like on https://store.wapt.frIt's simply a web server with packages and an index package file. The traditional practice is to place packages in a /wapt/ subdirectory at the root. For the package file, you need to have the wapt-scanpackages.py script installed on the machine.

The web interface of on https://store.wapt.fr This is purely cosmetic, allowing for a more elegant display of the list. However, a basic Apache package list will suffice. The Packages file is necessary to display packages directly in the WAPT console. Alternatively, you can also download and upload them locally from the console.

James wrote: ↑Oct 15, 2018 - 10:43 Perhaps we could consider, at a later stage, a mode that would allow us to synchronize the central repository across the different sites.

If you send packages directly to other repositories on other sites via direct synchronization, it implies that you are also responsible for the deployments on those sites. Indeed, according to WAPT security principles, a site's system administrator must resign their packages before deploying them; this is a way to validate which software is authorized on the network.

Sincerely,

Denis