misc. regular updates#1801
Conversation
| ```yaml | ||
| < < < < < < < HEAD | ||
| md5: 263395583f35403c8e0b1b94b30bea32 | ||
| ======= | ||
| md5: 520d2602f440d13372435d91d3bfa176 | ||
| > > > > > > > branch | ||
| frozen: true |
There was a problem hiding this comment.
@efiop another quick Q: this was added accidentally right? As .dvc files no longer have a top md5 field. Just double checking
There was a problem hiding this comment.
@jorgeorpinel This is an import file, so they do have the md5 and so this change is wrong 🙁
There was a problem hiding this comment.
- OK np I'll revert it.
Why do import .dvc files need a top md5 though? We may need to document this in https://dvc.org/doc/user-guide/dvc-files-and-directories or in the import(-url) refs. at least. Thanks
There was a problem hiding this comment.
We probably will be removing it in the future, it has been in discussions for a while now.
Indeed, looks like https://dvc.org/doc/user-guide/dvc-files-and-directories doesn't have imports at all 🙁
|
Sorry, this PR got too large somehow (I had an irregular week). But 9/16 files only have small indentation or typo changes. Hopefully it's not too much to review, but lmk if I should split it. Thanks |
| < < < < < < < HEAD | ||
| rev_lock: f31f5c4cdae787b4bdeb97a717687d44667d9e62 | ||
| ======= | ||
| = = = = = = = |
There was a problem hiding this comment.
they should be w/o spaces - https://wincent.com/wiki/Understanding_Git_conflict_markers ?
There was a problem hiding this comment.
The problem is that most IDEs will think it's an actual conflict if we save it like that. Maybe even GitHub or some code analyzers will pick it up as a problem.
There was a problem hiding this comment.
And we can't use HTML encoding since it's in a md code block.
| And then `dvc update` the `.dvc` file to download the latest data from its | ||
| original source. | ||
|
|
||
| > Note that updating will bring in the latest version of the data found in its |
shcheklein
left a comment
There was a problem hiding this comment.
looks good, some comments to fix, otherwise ready to merge
|
Thanks! Merging this but I can do a quick followup if any of the recent comments above require more iterations to be addressed. |
| Let's see an example using SSH. First, register and configure the remote: | ||
|
|
||
| ```dvc | ||
| $ dvc remote add myssh ssh://myserver.com | ||
| $ dvc remote modify --local myssh user myuser | ||
| $ dvc remote modify --local myssh password mypassword | ||
| ``` |
There was a problem hiding this comment.
This makes me realize our SSH examples for remote add/modify may be misleading (in other docs) because we sometimes use ssh://user@example.com... when adding, and then mention about modifying the credentials or even show an example of remote modify example user ... but I don't know if that will work correctly with DVC. Need to check...
There was a problem hiding this comment.
I tried testing this but can't because of treeverse/dvc#4712.
| Now, use an alias to this remote when defining the stage: | ||
|
|
||
| ```dvc |
There was a problem hiding this comment.
I also realized this doc only uses dvc run to define stages and doesn't show the resulting dvc.yaml files (except for import(-url) examples. Maybe we shouldn't even use dvc run in most of these examples? Since manually writing dvc.yaml is the recommended way.
But then again you can't easily write an external dependency in dvc.yaml ... Hmmm 🤔
statussample outputs (rel=Keepstatusoutput format consistents dvc#4490)