You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I work as an instructional designer, and I am attempting to install LRS SQL to demonstrate its benefits to the organization I work for. I have successfully installed it on Docker, but the interface I received is as shown in the attached picture. I believe some functions are missing. Where can I obtain my Endpoint link and query? How can I set up multiple LRS instances for each department within the organization? What is the recommended hosting service for installing this system? Is VPS the right choice? Additionally, are there any resources available that provide more information about this system?
The text was updated successfully, but these errors were encountered:
Hi @yasserBadr! By default your xAPI endpoint will be /xapi, but this can be configured with the LRSQL_URL_PREFIX env var see here. Once you have some data in the LRS you can view recorded statements from the "Statement Browser" tab.
SQL LRS is single-tenant, meaning that all credentials access the same group of statements. For an organization with multiple departments you would probably want to run multiple instances of SQL LRS. These can be connected to a combined LRS with LRSPipe if desired.
I work as an instructional designer, and I am attempting to install LRS SQL to demonstrate its benefits to the organization I work for. I have successfully installed it on Docker, but the interface I received is as shown in the attached picture. I believe some functions are missing. Where can I obtain my Endpoint link and query? How can I set up multiple LRS instances for each department within the organization? What is the recommended hosting service for installing this system? Is VPS the right choice? Additionally, are there any resources available that provide more information about this system?
The text was updated successfully, but these errors were encountered: