Skip to content
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

Allow installing a backend from a URL #2530

Closed
Tracked by #2164
TomAFrench opened this issue Sep 1, 2023 · 1 comment
Closed
Tracked by #2164

Allow installing a backend from a URL #2530

TomAFrench opened this issue Sep 1, 2023 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@TomAFrench
Copy link
Member

Problem

We need a good way to install different backends through nargo.

Happy Case

For an MVP we can allow a user to provide a backend name and an install url which serves a zipped tarball.

nargo backend install <backend name> <backend url>

This will create a directory in ~/.nargo/backends for this new backend which will hold any backend specific files (binary, crs, etc.)

If we're allowing installing through from a URL, we need to define a standard for how the backend binary should be contained within the tarball. For instance we currently assume that the binary will be the only file in the archive and that it exists at the root.

Alternatives Considered

No response

Additional Context

No response

Would you like to submit a PR for this Issue?

No

Support Needs

No response

@TomAFrench TomAFrench added the enhancement New feature or request label Sep 1, 2023
@github-project-automation github-project-automation bot moved this to 📋 Backlog in Noir Sep 1, 2023
@TomAFrench TomAFrench self-assigned this Sep 1, 2023
@TomAFrench
Copy link
Member Author

Addressed by #2575

@github-project-automation github-project-automation bot moved this from 📋 Backlog to ✅ Done in Noir Sep 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Archived in project
Development

No branches or pull requests

1 participant