Difference between revisions of "Deployment Platform/Internet"

Revision as of 08:05, 13 March 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:

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-desktop package;
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.

@@ Line 1: / Line 1: @@
 == Background ==
-This is [[Deployment_Platform/Deployment|one of possible]] deployment scenarios of [[Deployment Platform]].
+This is [[Deployment_Platform/Deployment|one of possible]] deployment scenarios of [[Deployment Platform]]. This page is intended to describe procedures for end users connected to the [[#Targeting_environment|Internet]].
-This page is intended to describe procedures for school servers and end users in the [[#Targeting_environment|Internet]] environment. Using [[#Recipes|predefined recipes]], it should be possible to fully support such deployments.
 === Targeting environment ===
@@ Line 12: / Line 10: @@
 * Server is located in the Internet and has singular access point.
-=== Objects ===
+== Server side ==
+For now, there are the following Sugar Network servers publicly available from the Internet:
+* [http://api-testing.network.sugarlabs.org/ api-testing.network.sugarlabs.org]<br>Recent stable release with data used in pilots; do not create temporal content here, use development server instead;
+* [http://api-devel.network.sugarlabs.org/ api-devel.network.sugarlabs.org]<br>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 {{Code|/etc/sweets.conf}} configuration file with the following options:
+ [client]
+ api-url = ''SERVER-API-URL-HERE''
-What kind of objects involved to the process:
+=== Run Sugar Network clients ===
-* '''Server'''<br>Sugar Network server accessible via the Internet via public API url. This tutorial is using http://api-testing.network.sugarlabs.org to refer to testing Sugar Network Master launched on Sugar Labs server.
+Right now, the easiest way to get working Sugar Network clients is using Sugar Shell with embedded Sugar Network support.
-* '''Clients'''<br>Users connected to the Server via the Internet. In server-less environment, users restricted only to content they already downloaded from the server.
+On XO laptops, use [[Deployment_Platform/XO_reference_distribution#Try_reference_implementation|one of reference images]] or final deployment ones like from [http://pe.sugarlabs.org/go/Proyecto_Piloto_Hexoquinasa Hexoquinasa] project.
-== Recipes ==
+On regular desktops:
-A list of use-cases to follow in the field.
+* [[Sweets_Distribution#Add_repository|Attach]] ''Factory'' [[Sweets Distribution]] repository;
+* [[Sweets_Distribution#Installation|Install]] {{Code|sweets-desktop}} package;
+* [[Sweets_Distribution#Usage|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, [[Platform_Team/Sugar_Network/Web_UI|Web UI]] client will be available from the Activities tray and the F8 shortcut key. [[Sugar_Network/Contributor_Hub|Contributor Hub]] client can be launched from F8 as regular Sugar Network application.
+Sugar Network client logs can be found {{Code|~/.sugar/default/logs/sugar-network-client}} file. Logging verbosity level depends on [[BugSquad/Get_Logs#Enabling_Sugar_debug_logging|global Sugar setting]].
+<!--
 === Client updates ===
@@ Line 41: / Line 59: @@
 * [[Deployment_Platform/Ubuntu_desktop_reference_distribution|Ubuntu desktop distribution]]<br>For users on Ubuntu.
 * [[Deployment_Platform/Debian_server_reference_distribution|Debian server distribution]]<br>For servers on Debian, Ubuntu or their derivates.
+--!>