Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings
This repository was archived by the owner on Nov 1, 2017. It is now read-only.

every curl needs optional s, and admin port#859

Merged
kdaigle merged 5 commits intomasterfromadmin_ports
Sep 22, 2015
Merged

Conversation

brntbeer
Copy link
Member

I know we warn about this in a tip in the top, but it's so subtle and easily missed. Is there any reason not to include this elsewhere? cc@leefaus who was helping me with this!

cc @github/docs or@gjtorikian

I know we warn about this in a tip in the top, but it's so subtle and easily missed. Is there any reason not to include this elsewhere?
@brntbeer
Copy link
MemberAuthor

also, just noticed the tip at the top of the page, but it's SO easy to miss.

I guess alternatively you could change the{tip}{/tip} to be a{warning}{/warning} at the top.

@gjtorikian
Copy link
Contributor

I'm definitely in favor of adding theadmin_port to everything--thanks for that!

I'm not so sure about thehttp(s) bit, though. Is there any reason we can't just keep it ashttp, orhttps? I'm trying to think of the newbie admin who isn't entirely sure what the(s) means.

@brntbeer
Copy link
MemberAuthor

@gjtorikian not to mention, languages. maybe it'd look weird for certain people.

If the port is 8080, it should be known from set up that it's http, and 8443 for https. That's a decent compromise 😉

@brntbeer
Copy link
MemberAuthor

@gjtorikian i think we're set on this if you want to give it another look.

I also noticed some responseLocation sections missing<em> tags aroundhostname. and i added those admin_ports to them too

@leefaus
Copy link

👍 Thanks to all for helping on this. I think this will make it easier for enterprise customers to consume these endpoints.

@@ -24,13 +24,13 @@ You need to pass your [Management Console password](https://help.github.com/ente
Use the `api_key` parameter to send this token with each request. For example:

<pre class="terminal">
$ curl -L 'http://<em>hostname</em>/setup/api?api_key=<em>your-amazing-password</em>'
$ curl -L 'http://<em>hostname</em>:<em>admin_port</em>:<em>admin_port</em>/setup/api?api_key=<em>your-amazing-password</em>'
Copy link
Contributor

Choose a reason for hiding this comment

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

Duplicated port info.

@gjtorikian
Copy link
Contributor

One tiny comment; when that's fixed feel free to merge. Thanks!

@brntbeer
Copy link
MemberAuthor

@gjtorikian great catch! updated

@brntbeer
Copy link
MemberAuthor

@gjtorikian just caught something, in other examples for enterprise, we put(s). like onhttps://developer.github.com/v3/users/administration. Thoughts?

@gjtorikian
Copy link
Contributor

Hmm. Since it's pointing to api.github.com, can we be bold and just switch 'em tohttps?

@leefaus
Copy link

@gjtorikian

Since the APIs are based on GitHub.com and on Enterprise customers, I think it would be valuable to call out both http and https as appropriate.

@kdaigle
Copy link
Member

@gjtorikian can I get your 👍 on this if it is good with@leefaus' final comments? It looks like you have that last piece of outstanding feedback. 😄

@@ -24,13 +24,13 @@ You need to pass your [Management Console password](https://help.github.com/ente
Use the `api_key` parameter to send this token with each request. For example:

<pre class="terminal">
$ curl -L 'http://<em>hostname</em>/setup/api?api_key=<em>your-amazing-password</em>'
$ curl -L 'http://<em>hostname</em>:<em>admin_port</em>/setup/api?api_key=<em>your-amazing-password</em>'
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybeconsole_port or mentionadmin_port specifically above?

@gjtorikian
Copy link
Contributor

@gjtorikian can I get your 👍 on this if it is good with@leefaus' final comments? It looks like you have that last piece of outstanding feedback. 😄

I'm definitely against the existinghttp(s), but let's also definitely punt on that for this PR.

I firmly believe The Right Thing to Do™ is:

  1. Changehttp(s) tohttps.

  2. Change the Enterprise script to replacehttps withhttp.

    We're already doing hella text substitutions whenever we generate the Enterprise docs, so we can add this one on too. I can take point for this work.

kdaigle added a commit that referenced this pull requestSep 22, 2015
every curl needs optional s, and admin port
@kdaiglekdaigle merged commit15f3bd7 intomasterSep 22, 2015
@kdaiglekdaigle deleted the admin_ports branchSeptember 22, 2015 23:12
@kdaigle
Copy link
Member

Thanks@gjtorikian! I merged this PR so you can tackle that work separately.

Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

5 participants
@brntbeer@gjtorikian@leefaus@kdaigle@MikeMcQuaid

[8]ページ先頭

©2009-2025 Movatter.jp