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

wasmer publish: Allow specifying a custom manifest file path #3949

Closed
theduke opened this issue Jun 5, 2023 · 0 comments · Fixed by #3953
Closed

wasmer publish: Allow specifying a custom manifest file path #3949

theduke opened this issue Jun 5, 2023 · 0 comments · Fixed by #3953
Assignees
Labels
🎉 enhancement New feature!

Comments

@theduke
Copy link
Contributor

theduke commented Jun 5, 2023

Currently only a directory can be specified, not a concrete manifest.toml file.

This can be useful for keeping multiple manifests in one directory.

@theduke theduke added the 🎉 enhancement New feature! label Jun 5, 2023
@theduke theduke self-assigned this Jun 5, 2023
theduke added a commit that referenced this issue Jun 5, 2023
Extends the "wasmer publish" command to allow specifying not just a
directory, but also a concrete "*.toml" manifest path.

This allows using manifests with a name other than the default
"wasmer.toml"

Useful for keeping multiple manifests in a single directory.

Closes #3949
theduke added a commit that referenced this issue Jun 5, 2023
Extends the "wasmer publish" command to allow specifying not just a
directory, but also a concrete "*.toml" manifest path.

This allows using manifests with a name other than the default
"wasmer.toml"

Useful for keeping multiple manifests in a single directory.

Closes #3949
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🎉 enhancement New feature!
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant