Deployment Platform/Gateway: Difference between revisions

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;

[[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):

  # path to a directory to place server data

  data-root = /var/lib/sugar-network

Make sure that all directories in config file are created and current user have write permissions there.

Note that newly installed Sugar Network node will be empty, its content should be fetched from the master node.

Last command path will contain files that should be uploaded to the master to download response. Postponed synchronization will happen by running {{Code|sugar-network-sync}} shell script (which will be created by {{Code|offline-sync}} command in targeting path) in environment with Internet connectivity. Then, re-run {{Code|offline-sync}} command specifying path with new file synchronization files.

=== 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:

=== Run Sugar Network clients ===

Right now, the easiest way to get working Sugar Network clients is using Sugar Shell with embedded Sugar Network support.

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]].