Demo setup/generators supporting different setup scenarios #1893
Labels
Status: Community Help Wanted (good first issue)
simple tasks that don't require understanding every last detail of our platform
Comments
sleidig
added
the
Status: Idea
|
This is actually a more important problem now, because keycloak login (which is required now) doesn't allow to use the app in an iframe (which we are doing to display the username + password to website visitors). Current demos are:
|
sleidig
added
Type: Bug
Status: Community Help Wanted (good first issue)
sleidig
moved this from Triage / Analysis
to Todo (ready for work)
in All Tasks & Issues
sleidig
moved this from Todo (ready for work)
to Triage / Analysis
in All Tasks & Issues
kumarannathan
added a commit
to kumarannathan/ndb-core
that referenced
this issue
Dec 10, 2024
Pushing Commit for my EECS481 Partner as they were not able to due to not being a collaborator within github. Added functionality to DemoDataInitializerService: • Reads demo_entities.json from the assets folder. • Logs a message if the file is found or defaults to the existing hardcoded setup if not. • Prepares for future insertion of JSON data into the database for scenario-specific demo customization. Co-Authored-By: Mira Panjaitan <[email protected]>
kumarannathan
added a commit
to kumarannathan/ndb-core
that referenced
this issue
Dec 10, 2024
This reverts commit 77f8298.
kumarannathan
added a commit
to kumarannathan/ndb-core
that referenced
this issue
Dec 10, 2024
Pushing for my partner on the project, as she was not added as a collaborator and couldn't make a PR. Added functionality to DemoDataInitializerService: • Reads demo_entities.json from the assets folder. • Logs a message if the file is found or defaults to the existing hardcoded setup if not. • Prepares for future insertion of JSON data into the database for scenario-specific demo customization. Co-Authored-By: Mira Panjaitan <[email protected]>
Draft
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In practice, we are running multiple demo sites for different use cases (e.g. education, health, vocational training). However, the code only supports a single demo setup (config-fix.ts) and the demo data generator services have hard-coded parameters on what to generate. As a workaround, other demo systems are actually run in "synced" mode and cannot auto-generate new data every time a user visits the site.
Requirements / Suggested implementation:
demo_entities.jsonthat contains docs to be saved into the database in demo mode (after the demo generators ran?)Sample demo_entities.json:
{ "docs": [ { "_id": "Config:CONFIG_ENTITY", "otherField": "xyz" }, { /* other doc to be saved using `_bulk_docs` */ } ] }The text was updated successfully, but these errors were encountered: