-
Notifications
You must be signed in to change notification settings - Fork 44
Installation
- Java - 8+
sunbird_sso_publickey = ******
sunbird_sso_realm=sunbird
sunbird_sso_url=https://dev.open-sunbird.org/auth/
git clone git@github.com:project-sunbird/open-saber.git
sh configure-dependencies.shThis should install default configuration, which will configure resource files required for a Teacher Registry on your machine.
Edit the configuration files or create your own custom configuration files and configure the path. Read understanding configuration files in the section below. If you just want to try it out, then skip this section and come back to it later.
-
Configuring custom configuration files
1. Read understanding configuration files in the section below to create your own configuration files
2. Add environment variables pointing to the configuration files.
registry_config_dir=file://...
config_schema_file=${registry_config_dir}schema-configuration.jsonld
validations_create_file=${registry_config_dir}validations_create.shex
validations_update_file=${registry_config_dir}validations_update.shex
frame_file=${registry_config_dir}frame.json
audit_frame_file=${registry_config_dir}audit_frame.json
cd open-saber/java
mvn clean installcd open-saber/java/registry
mvn clean installAll dependencies are now installed. All required sample configuration files are also created and if you don't want to change anything, you may simply follow the following steps to start up an opensaber instance as a Teacher Registry.
cd opensaber/java/registry
docker-compose upcd opensaber/java/registry/target
java -jar registry.jarBelow mentioned configuration files should be created in src/main/resources. The script ./configure-dependencies.sh will create the files to startup a full fledged Teacher Registry, but you can edit these files to suit your domain. The sample files contain comments which further explain each property.
-
application.yml - Create a YAML configuration file which contains various environment specific configurations for the application. The default profile will be development environment. The spring.profiles.active configuration needs to be changed to the environment where the application is deployed. Sample configuration details can be found application.yml.sample.
-
validations_*.shex - These file(s) should contain static and declarative validations. For further details on syntax, you can refer to the Shape Expressions Primer(Shex Primer). Two separate files are required during creation and updation of entities. An example for the validations can be found validation_create.shex.sample.
-
schema-configuration.jsonld - This file should contain schema level configurations. Further details can be found schema-configuration.jsonld.sample.
-
frame.json - This file is useful to frame the JSONLD output so that all the facts are nested instead of being flatly presented. This helps in readability. frame.json.sample contains short-hand names, their namespaces and the the primary type used throughout the JSON-LD document that is issued into the registry.
-
audit_frame.json - If audit is enabled in application.yml, this file is useful to frame the audit records so that all the facts are nested instead of being flatly presented. This helps in readability. audit_frame.json.sample contains short-hand names, and their namespaces used throughout the audit record that is issued into the registry.
Create a domain specific vocabulary file for the application. Sample vocabulary file can be found vocabulary.owl.sample. This file should be placed in src/main/resources/vocabulary, so that it can be served as a static resource. This is useful for machine readability of your registry and also helps in understanding various terms being used in the vocabulary.