Deployment Platform/Internet
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:
- api-testing.network.sugarlabs.org
Recent stable release with data used in pilots; do not create temporal content here, use development server instead;
- api-devel.network.sugarlabs.org
Development server which does not contain important data and free for any experiments (administrative privileges for anonymous users).
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
Run Sugar Network clients
Right now, the easiest way to get working Sugar Network clients is using Sugar Shell with embedded Sugar Network support.
On XO laptops, use one of reference images or final deployment ones like from Hexoquinasa project.
On regular desktops:
- Attach Factory Sweets Distribution repository;
- Install
sweets-desktoppackage; - Run newly installed Sugar Shell;
- By default, Sugar Shell looks the same as in pristine Glucose. To start using Sugar Network related improvements in the Shell UI, go to the Sweets Distribution component in the Control Panel, enable the integration checkbox, and restart Sugar. After restarting, Web UI client will be available from the Activities tray and the F8 shortcut key. Contributor Hub client can be launched from F8 as regular Sugar Network application.
Sugar Network client logs can be found ~/.sugar/default/logs/sugar-network-client file. Logging verbosity level depends on global Sugar setting.