Sugar Network/API: Difference between revisions
mNo edit summary |
|||
| Line 34: | Line 34: | ||
* [http://node.sugarlabs.org/ node.sugarlabs.org]<br>Production server; | * [http://node.sugarlabs.org/ node.sugarlabs.org]<br>Production server; | ||
* [http://localhost:5001/ localhost:5001]<br>default url to get access to [[# | * [http://localhost:5001/ localhost:5001]<br>default url to get access to [[#Client_API|local proxy]] provided from user side application. | ||
== Sugar Network resources == | == Sugar Network resources == | ||
| Line 155: | Line 155: | ||
=== Authentication === | === Authentication === | ||
Right now, the only way to be authenticated on a Sugar Network server is by running a [[Platform_Team/Sugar_Network/Implementation#sugar-network-client|local application]] on the client side and using the API it [[# | Right now, the only way to be authenticated on a Sugar Network server is by running a [[Platform_Team/Sugar_Network/Implementation#sugar-network-client|local application]] on the client side and using the API it [[#Client_API|provides]]. | ||
''TODO'' | ''TODO'' | ||
| Line 331: | Line 331: | ||
== Usage == | == Usage == | ||
Being HTTP based, Sugar Network API can be used in any manner regular HTTP requests can be handled. But for command-line access, there is a handy tool, {{Code|sugar-network}}, which takes care about Sugar Network specific like launching local API (if it is not already available) to get access to [[# | Being HTTP based, Sugar Network API can be used in any manner regular HTTP requests can be handled. But for command-line access, there is a handy tool, {{Code|sugar-network}}, which takes care about Sugar Network specific like launching local API (if it is not already available) to get access to [[#Client_API|local proxy]]. | ||
The sugar-network command-line format is below. Call {{Code|sugar-network --help}} for more detailed info. | The sugar-network command-line format is below. Call {{Code|sugar-network --help}} for more detailed info. | ||