5,705
edits
Changes
Jump to navigation
Jump to search
Deployment Platform/Gateway (view source)
Revision as of 05:50, 13 March 2013
, 05:50, 13 March 2013Created page with "== Background == This is one of possible deployment scenarios of Deployment_Platform. This page is intended to describe procedures for ..."
== Background ==
This is [[Deployment_Platform/Deployment|one of possible]] deployment scenarios of [[Deployment_Platform]]. This page is intended to describe procedures for school servers that behave as gateways for school students.
=== Targeting environment ===
The standard targeting environment, final environment might be similar, assumes:
* School server;
* Client machines connected via Intranet to the server.
== Server side ==
=== Run Sugar Network node ===
[[Sweets_Distribution#Add_repository|Attach]] ''Factory'' [[Sweets Distribution]] repository and install {{Code|sugar-network}} package.
Before running server, populate the {{Code|/etc/sugar-network/config}} configuration file with content similar to following (to get full list of configuration options, call the {{Code|sugar-network-node config}} command):
[main]
# path to a directory to place log files
logdir = /var/log/sugar-network
# path to a directory to place pid files
rundir = /var/run/sugar-network
# if specified, use this directory for cached files; such files might take
# considerable number of bytes
cachedir = /var/cache/sugar-network
[node]
host = 0.0.0.0
port = 8000
# path to a directory to place server data
data-root = /var/lib/sugar-network
# switch off user credentials check; disabling this option will require
# OpenSSH-5.6 or later
trust-users = True
Make sure that all directories in config file are created and current user have write permissions there.
Run node server:
sugar-network-node start
Server will start serving Sugar Network [[Platform_Team/Sugar_Network/API|API]] for clients from {{Code|host}}:{{Code|port}} specified in configuration file.
=== Synchronization with master node ===
== Client side ==
=== Configuration ===
Clients should be pointed to the Sugar Network node launched on a school server. Populate {{Code|/etc/sweets.conf}} configuration file with the following options:
[client]
api-url = http://''SCHOOL-SERVER-HOST-HERE'':8000
=== Install Sugar Network clients ===
Right now, the easiest way to get working Sugar Network clients is using Sugar Shell with embedded Sugar Network support.
On regular desktops:
* [[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.
This is [[Deployment_Platform/Deployment|one of possible]] deployment scenarios of [[Deployment_Platform]]. This page is intended to describe procedures for school servers that behave as gateways for school students.
=== Targeting environment ===
The standard targeting environment, final environment might be similar, assumes:
* School server;
* Client machines connected via Intranet to the server.
== Server side ==
=== Run Sugar Network node ===
[[Sweets_Distribution#Add_repository|Attach]] ''Factory'' [[Sweets Distribution]] repository and install {{Code|sugar-network}} package.
Before running server, populate the {{Code|/etc/sugar-network/config}} configuration file with content similar to following (to get full list of configuration options, call the {{Code|sugar-network-node config}} command):
[main]
# path to a directory to place log files
logdir = /var/log/sugar-network
# path to a directory to place pid files
rundir = /var/run/sugar-network
# if specified, use this directory for cached files; such files might take
# considerable number of bytes
cachedir = /var/cache/sugar-network
[node]
host = 0.0.0.0
port = 8000
# path to a directory to place server data
data-root = /var/lib/sugar-network
# switch off user credentials check; disabling this option will require
# OpenSSH-5.6 or later
trust-users = True
Make sure that all directories in config file are created and current user have write permissions there.
Run node server:
sugar-network-node start
Server will start serving Sugar Network [[Platform_Team/Sugar_Network/API|API]] for clients from {{Code|host}}:{{Code|port}} specified in configuration file.
=== Synchronization with master node ===
== Client side ==
=== Configuration ===
Clients should be pointed to the Sugar Network node launched on a school server. Populate {{Code|/etc/sweets.conf}} configuration file with the following options:
[client]
api-url = http://''SCHOOL-SERVER-HOST-HERE'':8000
=== Install Sugar Network clients ===
Right now, the easiest way to get working Sugar Network clients is using Sugar Shell with embedded Sugar Network support.
On regular desktops:
* [[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.