Kirill

@cambierr thanks for recommendation. How do you suggest implementing it? All repositories provide REST HTTP API, I'm not sure any client can support FTP

> well.. I think the easiest way is to use a different entry-point (server) that relies on the common infrastructure. I may build a quick proof of concept of a...

@olenagerasimova @genryxy please update the page for repositories you are working on

@aiovlev we created a task for Conan local repository: https://github.com/artipie/conan-adapter/issues/1, when ready we'll integrate it to Artipie.

I think we need to start with a version details here.

@dgarus this issue is actually about making all optional dependencies (like s3, etcd, vertx, etc) as `provided` in asto, http and other main dependencies. And provide them in main artipie...

@olenagerasimova previously Artipie dashboard was working with GitHub oauth authorization, without generating tokens manually. https://docs.github.com/en/developers/apps/building-oauth-apps/authorizing-oauth-apps

@PeterGrace we started Cargo repository here: https://github.com/artipie/cargo-adapter and we notify you when it will be integrated to Artipie server.

I think we can use `aliases` optional list, not just single alternative login string: ```yaml joe: aliases: - [email protected] - [email protected] pass: "plain:123" ```

@yegor256 yes, I can do it