Page 1 of 1

Specifications for building a (shared) repository

Published: May 30, 2018 - 10:13
by olivetree
Hello

, I'd like to create a WAPT repository available not just for my lab but for all units within my administration, in order to share packages. Creating a separate, private system for my administration isn't ideal.
I'd like to know if there are specific requirements to follow or if there's sufficient documentation for someone to undertake this task. Why just one person? Because there are always more people who take advantage of, use, or even abuse a service than there are people who actually create and implement it.

If this is a bad idea, please let me know. :)

Re: Specs for building a (shared) repository

Published: May 30, 2018 - 6:38 PM
by sfonteneau
I'm having trouble fully understanding the goal.

If I understand correctly, your aim is to offer your packages to your colleagues?

In that case, your colleagues simply need to specify your repository in the "import from internet" field.

When they want to duplicate a package from your repository, they select it.

Alternatively, I did something similar two years ago:

https://github.com/sfonteneau/repo_wapt_collaboratif