Difference between revisions of "Deployment Platform/Internet"
Jump to navigation
Jump to search
m (→Client side) |
|||
| Line 22: | Line 22: | ||
== Client side == | == Client side == | ||
| − | = | + | <h3 id="Configuration">Configuration</h3> |
Point clients to one of existing Sugar Network servers by populating {{Code|/etc/sweets.conf}} configuration file with the following options: | Point clients to one of existing Sugar Network servers by populating {{Code|/etc/sweets.conf}} configuration file with the following options: | ||
Revision as of 10:59, 3 June 2013
Background
This is one of possible deployment scenarios of Deployment Platform. This page is intended to describe procedures for end users connected to the Internet.
Targeting environment
The standard targeting environment assumes:
- End users have reliable Internet connectivity all time.
- Server is located in the Internet and has singular access point.
Server side
For now, there are the following Sugar Network servers publicly available from the Internet:
- node-devel.sugarlabs.org
Development server which does not contain important data and is free for any experiments (administrative privileges for anonymous users);
- node-testing.sugarlabs.org
Recent stable release with regular data import from the production server; is still free for any experiments;
- node.sugarlabs.org
Production server.
Client side
Configuration
Point clients to one of existing Sugar Network servers by populating /etc/sweets.conf configuration file with the following options:
[client] api-url = SERVER-API-URL-HERE
By default, clients look for production server.
Run Sugar Network clients
Follow the Try it install instructions to setup Sugar Network client.
While working, Sugar Network client logs can be found ~/.sugar/default/logs/sugar-network-client file. Logging verbosity level depends on global Sugar setting.