8000 Backport #2116 to releases/2.5 by mdlinville · Pull Request #2122 · distribution/distribution · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Backport #2116 to releases/2.5 #2122

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

Merged
merged 1 commit into from
Jan 3, 2017
Merged

Backport #2116 to releases/2.5 #2122

merged 1 commit into from
Jan 3, 2017

Conversation

mdlinville
Copy link
Contributor

Improve formatting of configuration.md

Backported from master to release/2.5

Signed-off-by: Misty Stanley-Jones misty@docker.com

< 8000 div class="avatar-parent-child TimelineItem-avatar d-none d-md-block"> @dmcgowan
Copy link
Collaborator
dmcgowan commented Jan 3, 2017

Can you cherry pick your original commit rather than the merge commit?

@mdlinville
Copy link
Contributor Author

I can, in docker/docker they prefer the merge commit. is there a way for me to redo it without having to resolve 39 conflicts again?

@dmcgowan
Copy link
Collaborator
dmcgowan commented Jan 3, 2017

@mstanleyjones no need to re-resolve, you can just edit the commit message. I have never seen it done that way in docker/docker. I prefer to have the original commit message as the cherry pick commit message and I find the merge commit message confusing given the context.

@mdlinville mdlinville changed the title Merge pull request #2116 from mstanleyjones/fix_config_ref_formatting Backport #2116 to releases/2.5 Jan 3, 2017
@mdlinville
Copy link
Contributor Author

OK I changed the commit message.

Copy link
Collaborator
@dmcgowan dmcgowan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like a few more rebase changes needed

storage:
filesystem:
rootdirectory: /var/lib/registry
maxthreads: 100
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This got moved, should be same level as rootdirectory

You can use the `redirect` storage middleware to specify a custom URL to a
location of a proxy for the layer stored by the S3 storage driver.

|-----------|----------|-------------------------------------------------------------------------------------------------------------|
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

missing line for

| Parameter | Required | Description                                                                                                 |

|-----------|----------|-------------------------------------------------------------------------------------------------------------|
| `baseurl` | yes | `SCHEME://HOST` at which layers are served. Can also contain port. For example, `https://example.com:5443`. |

## `reporting`

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This must have been part of a different change in master, but in master this is surrounded by ```

| `threshold`| no | The number of times the check must fail before the state is marked as unhealthy. If this field is not specified, a single failure marks the state as unhealthy. |


## `proxy`

proxy:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same with this section, is surrounded by ```

privatekey: /path/to/asecret.pem
keypairid: asecret
duration: 60

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

missing ```

Backported from master to release/2.5

Signed-off-by: Misty Stanley-Jones <misty@docker.com>
@mdlinville
Copy link
Contributor Author

Addressed the feedback. Will double-check in #2123 as well.

@codecov-io
Copy link

Current coverage is 52.62% (diff: 100%)

Merging #2122 into release/2.5 will decrease coverage by 10.14%

@@           release/2.5      #2122   diff @@
=============================================
  Files              120        120           
  Lines            10496      10496           
  Methods              0          0           
  Messages             0          0           
  Branches             0          0           
=============================================
- Hits              6589       5524   -1065   
- Misses            3032       4232   +1200   
+ Partials           875        740    -135   

Powered by Codecov. Last update 6b114e6...fcbea60

Copy link
Collaborator
@dmcgowan dmcgowan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@dmcgowan dmcgowan merged commit 9bc9d21 into distribution:release/2.5 Jan 3, 2017
@mdlinville mdlinville deleted the configuration_changes_backport branch January 3, 2017 23:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0