New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tracking issue for RFC 2141: Add support to Cargo for alternative registries #44931

Open
aturon opened this Issue Sep 29, 2017 · 16 comments

Comments

Projects
None yet
@aturon
Member

aturon commented Sep 29, 2017

This is a tracking issue for the RFC "Add support to Cargo for alternative registries" (rust-lang/rfcs#2141).

Steps:

Unresolved questions:

  • Are the names of everything what we want?

    • cargo generate-index-metadata?
    • registry = my-registry?
    • publish-registries = []?
  • What kinds of authentication parameters do we need to support in .cargo/credentials?

@matklad

This comment has been minimized.

Member

matklad commented Oct 1, 2017

I think PR is already in flight: rust-lang/cargo#4506

@cswindle

This comment has been minimized.

cswindle commented Oct 4, 2017

I have PR for adding the parts in the RFC about changes to publish: rust-lang/cargo#4568

@est31

This comment has been minimized.

Contributor

est31 commented Nov 12, 2017

I've encountered some issues with the official crates.io index. It appears to be non-conformant to the spec: rust-lang/crates.io#1168

@ninrod

This comment has been minimized.

ninrod commented Feb 26, 2018

Hi, this issue seems to target enterprise usage. This means artifactory support, which is really the standard in enterprise, right? Right now I want to use rust in my company and cannot because of that.

Would it be useful to add a bullet like: "works in artifactory"?

@wycats

This comment has been minimized.

Contributor

wycats commented Feb 26, 2018

@ninrod I think we'd want to get some eyeballs and feedback from Artifactory, but I don't necessarily think we need to wait to stabilize until they actually implement.

@wycats

This comment has been minimized.

Contributor

wycats commented Feb 26, 2018

@stuhood

This comment has been minimized.

stuhood commented Feb 26, 2018

@ninrod : Bumps on https://www.jfrog.com/jira/browse/RTFACT-13469 would be appreciated.

@ccojocar

This comment has been minimized.

ccojocar commented Jun 29, 2018

What's the current state of this issue? Has anyone managed to use Nexus for cache purposes? The dependencies installation is kind of slow, especially on an ephemeral build system. Thanks

cc @rawlingsj

@aaronsky

This comment has been minimized.

aaronsky commented Jul 2, 2018

Very interested in Artifactory support for Cargo. I want to start pushing Rust more at my company but if I can't use Artifactory rather than crates.io, distribution is made much more difficult.

@gilescope

This comment has been minimized.

Contributor

gilescope commented Jul 19, 2018

How are we doing? Is there something I can try out in my company? And also do we need to team up and create an artifactory plugin?

Really this should be tagged Rust 2018 edition (if not earlier), because if we can't use Rust at work what's the point?

@aaronsky

This comment has been minimized.

aaronsky commented Jul 19, 2018

Speaking personally, I don't know what's involved in creating an Artifactory plugin for something of this potential scale. I have been trying to find some information or examples on how folks in other communities have approached bootstrapping rudimentary Artifactory support for their ecosystem. I have also been ramping up on Cargo and how to implement the missing pieces outlined in the tracking issue.

I would love to help more seriously with this effort as it is a deciding factor on whether we can use Rust at my organization.

@ebkalderon

This comment has been minimized.

ebkalderon commented Jul 31, 2018

Not having support for alternative registries in Cargo is a massive pain. Working with private Git dependencies gets rather difficult at scale, and having private registries would make our lives so much easier.

@cswindle

This comment has been minimized.

cswindle commented Jul 31, 2018

@aaronsky, I did some work creating a server which is able to act as a registry https://crates.io/crates/caesium, this allows having different plugins to interface to different storage backends, one of which is artifactory. Please note that it does not offer a web frontend, but it does give the ability to upload crates to artifactory and update the git backend. This was mainly developed for testing some of the alternative registries code rather than actually running a production system.

@boskiv

This comment has been minimized.

boskiv commented Sep 29, 2018

Does anyone used https://crates.io/crates/caesium?
Is there some instruction how to publish crate there ?

@boskiv

This comment has been minimized.

boskiv commented Sep 29, 2018

Guys, Is there any updates or milestones for this issue ? May be there is some workarounds ? From DevOps perspective it's a very complicated today to manage private dependencies.

@ahmedcharles

This comment has been minimized.

Contributor

ahmedcharles commented Oct 19, 2018

The RFC doesn't specify which characters are valid in fields in the registry index data. Is it possible to clarify that? E.g. Is a crate name allowed to contain '@', '#' or '$'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment