-
Notifications
You must be signed in to change notification settings - Fork 192
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
Add 'verdi node copyfiles' command #1121
Comments
I personally don't like it too much, because it suggests people that it's good to go there (and potentially mess up with files). If really needed, I would just add a command that prints the URI of the repository, and then the user will do what he wants (this will work also with the object store). However, I'd rather think to improve ways to view the files can be accessed. Suggestions open, but e.g.
I think both points above are good and probably easy to do, at least in their basic version. P.S.: If you didn't know that 'verdi node repo ls/cat' existed, probably it's a lack of documentation/documentation in the wrong place/not intuitive name, any suggestions welcome on how to improve. |
I did know that these commands exist, but they don't help much in the case of binary (HDF5, pdf) files. If I remember right I just used tab completion or I totally see your point about not wanting people to meddle in the repository. Copying out the files is absolutely the better idea here. |
Great! I think it should be pretty straightforward to implement then. |
This feature request resurfaced during the May tutorial |
For inspecting results from the command-line, it would be nice to have an easy way to see output files, especially for
SinglefileData
orFolderData
. What do you think about adding averdi node gotorepository
command, which takes you to the node's repository folder.Or does this collide with the plans to add an object store backend for the repository? I could also see simply printing something like "This feature is not supported with the object-store repository." in that case.
The text was updated successfully, but these errors were encountered: