You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/user/googledevconsole_api.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,19 +35,19 @@ Optional APIs are only used if you got the right modules or a payment type to us
35
35
36
36

37
37
38
-
## 4 - Generate an API Key
39
-
GDC API services only need one key for all Google Services used. You must generate a key for each bot instance you plan to use. Go to **APIs and Auth -> Credentials** then select ***Create a new Key***
38
+
## 4 - Generate an API Key
39
+
GDC API services only need one key for all Google Services used. You must generate a key for each bot instance you plan to use. Go to **APIs and Auth -> Credentials** then select ***Create a new Key***
40
40
41
41

42
42
43
-
Select to create a ***Server Key***
43
+
Select to create a ***Server Key***
44
44
45
45

46
46
47
-
Enter the Public IPs of the Cloudbot instance you plan to assign to this key. If you don't know it, running `wget -qO- http://icanhazip.com/` within your terminal should return it. Click ***Create***.
47
+
Enter the Public IPs of the Cloudbot instance you plan to assign to this key. If you don't know it, running `wget -qO- http://icanhazip.com/` within your terminal should return it. Click ***Create***.
48
48
49
49

50
50
51
-
Your new key should now appear on the main panel, simply copy it to the *google_dev_key* object in your CloudBot's configuration.
51
+
Your new key should now appear on the main panel, simply copy it to the *google_dev_key* object in your CloudBot's configuration.
52
52
53
53

0 commit comments