-
Notifications
You must be signed in to change notification settings - Fork 197
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
Adding questions/answers to spec #189
Conversation
spec.md
Outdated
@@ -133,7 +133,44 @@ If the blob is not found in the registry, the response code MUST be `404 Not Fou | |||
|
|||
#### Push | |||
Pushing an image works in the opposite order as a pull: the blobs making up the layers are pushed first, and the | |||
manifest last. | |||
manifest last. A useful diagram is provided [here](https://github.com/google/go-containerregistry/tree/d7f8d06c87ed209507dd5f2d723267fe35b38a9f/pkg/v1/remote#anatomy-of-an-image-upload). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we don't want to just link out to another repo but find it useful, the source for this is here: https://github.com/google/go-containerregistry/blob/master/images/dot/upload.dot
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be redundant to re-host it, and what if the other version changes but ours does not? What do others think?
@vsoch this is good stuff. Do you think it makes sense in its own FAQ section at bottom? Regarding links etc., please see #188 where we are adding an appendix. Also - can you fix the travis build?
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good content, but majority should be placed into a top-level ## F.A.Q.
section right before the API section. For links to diagrams, we can add them to the appendix
@jdolitsky @jonjohnsonjr that's a good idea to have them in FAQ - but is there a way we can link them back to where they are relevant? We'd want the person reading / implementing to read points when they are relevant, otherwise they might be missed entirely. Maybe a link from the FAQ back to the section, so for the section, a small list of relevant FAQ at the end of each? |
okay I've moved all the question snippets into it's own FAQ section - it's not ideal in that it becomes unlinked from the relevant sections, but hopefully having it right before the specification sections (push, etc.) the user will at least glance over it and know to come back if there is a question. |
I wonder whether this content should move to a separate "advice for implementors" or "implementation guide" document. That would accomplish a few goals:
|
@adamwg I'm happy to do that, just let me know what you want. Also, it looks like there was a merge so now there is a merge conflict. I can attempt to resolve but I may not be familiar enough with what should be there to do it correctly. |
okay looks like I was able to do it! Hopefully correctly, haha. |
+1 to Adam's comment. This document could (and should) grow pretty large. Howabout an |
or just in the main README of distribution spec in a sub section so it's
easy to find?
…On Thu, Oct 8, 2020 at 10:14 AM Josh Dolitsky ***@***.***> wrote:
+1 to Adam's comment. This document could (and should) grow pretty large.
Howabout an faq.md ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#189 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAPSINWF5NKJ5SKGV5335LSJXJORANCNFSM4RY4GEEA>
.
--
Cheers,
Chris Aniszczyk
http://aniszczyk.org
+1 512 961 6719
|
That works as well. image-spec has something similar: https://github.com/opencontainers/image-spec |
Moved. |
@vsoch awesome. Can you fix the signoff error? |
How exactly? I merged master into here from the interface, and here is the git history. Are you saying I have to start from scratch? Why is it so hard to contribute here? :(
|
Signed-off-by: vsoch <vsochat@stanford.edu>
I started from scratch and updated the files, I hope that worked. :/ |
@vsoch I understand the pain. Looks like it worked |
@vsoch - apologies, but there was some conversation about this - can we move this into an |
Sure thing! Let me pull and make the changes. |
Signed-off-by: vsoch <vsochat@stanford.edu>
@vsoch - looks good, can you fix the sign-off issue? One of the commits must be missing it |
All of the commits are signed (see verified in the Commits tab). What am I missing? |
I had to update from master (there was a merge conflict), I did that on GitHub automatically. |
During start of implementation for the distribution spec, I had a lot of basic questions about different scenarios and modeling, and (even if the spec doesn't have a definitive answer) I think it would be helpful to include more detail to help the reader/user. The pull request here will cover most of the discussion in #184, adding questions -> answers along with the spec details to help guide the reader. Please feel free to make suggests to wording or content!
Signed-off-by: vsoch vsochat@stanford.edu