Download the PHP package oat-sa/extension-tao-offline without Composer

On this page you can find all versions of the php package oat-sa/extension-tao-offline. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package extension-tao-offline

TAO Offline Extension

TAO Logo

GitHub GitHub release GitHub commit activity

TAO Offline Capability offers schools the possibility to take assessments in environments with unstable internet connections. It uses Virtual Machines (VM) and a Central Server (CS). The assessment is performed on the VMs that contain a TAO installation as well as the tests. At the end the results of the test will be synchronized with the Central Server.

Installation instructions

These instructions assume that you already have a TAO installation on your system. If you don't, go to package/tao and follow the installation instructions.

Add the extension to your TAO composer and to the autoloader:

Install the extension on the CLI from the project root:

Linux:

Windows:

As a system administrator you can also install it through the TAO Extension Manager:

Synchronization and Encryption

Synchronization

The synchronization process is based upon two actors, the Client Server, which is installed on a Virtual Machine, and the Central Server.

Setting up the Client Server

The following script needs to be run on a TAO instance in order to create a Client Server:

On systems where extension-tao-encryption is installed, the script will set it up with encryption.

Point the instance to a specific server by executing the following command:

Setting up the Central Server

Run the following to turn a TAO instance into a Central Server.

Again, instances with taoEncryption will benefit from encryption.

Types of available synchronizations

Overview of the workflow

Sequence Diagram

Synchronizing users with encryption

Every user has been assigned an application key that is used to decrypt the delivery content. Properties that are excluded from the synchronization process can be found under excludedProperties in the configuration file config/taoSync/syncService.conf.php. Properties that are encrypted are defined inside config/taoEncryption/encryptUserSyncFormatter.conf.php.

Synchronizing deliveries with encryption

During the synchronization of the deliveries, the test package is sent to the client. The client then imports the test and generates a delivery.

Note: If you are synchronizing a delivery that already exists on the VM a new import of the test will be created.

Synchronizing results with encryption

The chunkSize of a result is an essential configuration parameter that needs to be set in advance; the default is 10. It can be set depending on the number of variables included in a result.

If you have, for example, a test with 100 items (which means about 400 variables), the total request will contain about 4000 variables. This scenario is likely to overload the server. In this case, reducing the chunkSize to a smaller value is advised.

The statuses of a result that needs to be sent can be configured under statusExecutionsToSync in config/taoSync/resultService.conf.php. Each request to the server will include the number of results. The process will stop after all results have been sent.

Synchronizing results - Logs

Each result log is synchronized with the Central Server to maintain a history of the test. The number of logs sent per request is defined in the configuration inside config/taoSync/SyncDeliveryLogService.conf.php.


All versions of extension-tao-offline with dependencies

PHP Build Version
Package Version
Requires oat-sa/oatbox-extension-installer Version ~1.1||dev-master
oat-sa/generis Version >=14.0.0
oat-sa/tao-core Version >=47.0.0
oat-sa/extension-tao-sync Version >=8.0.0
oat-sa/extension-tao-testcenter Version >=10.0.0
oat-sa/extension-tao-delivery-rdf Version >=14.0.0
oat-sa/extension-tao-proctoring Version >=20.0.0
oat-sa/extension-tao-encryption Version >=6.0.0
oat-sa/extension-tao-oauth Version >=6.0.0
oat-sa/extension-tao-publishing Version >=6.0.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package oat-sa/extension-tao-offline contains the following files

Loading the files please wait ....