src/backend/demo/defaults.py

"""Parameters that define how the demo site will be built."""

NB_OBJECTS = {
    "users": 50,
    "docs": 50,
    "max_users_per_document": 50,
}

DEV_USERS = [
    {"username": "impress", "email": "impress@impress.world", "language": "en-us"},
    {"username": "user-e2e-webkit", "email": "user@webkit.e2e", "language": "en-us"},
    {"username": "user-e2e-firefox", "email": "user@firefox.e2e", "language": "en-us"},
    {
        "username": "user-e2e-chromium",
        "email": "user@chromium.e2e",
        "language": "en-us",
    },
]
🤡(demo) generate dummy user To search users we need to have some dummy data users. We add some dummy users when we run the `make demo` command. 2024-05-30 15:57:11 +02:00			`"""Parameters that define how the demo site will be built."""`

			`NB_OBJECTS = {`
🤡(demo) demo generate dummy documents The demo command will generate dummy documents and dummy accesses. 2024-07-04 16:40:19 +02:00			`"users": 50,`
			`"docs": 50,`
			`"max_users_per_document": 50,`
🤡(demo) generate dummy user To search users we need to have some dummy data users. We add some dummy users when we run the `make demo` command. 2024-05-30 15:57:11 +02:00			`}`
🌱(demo) create dev users and make them doc accesses To be able to test with dummy data, we need to create our dev users from the demo and to give them access to the docs. The sub is the unicity of the user for our oidc provider, so we need to know the sub to be able to create correctly the user, it is why we set the sub as the email of the user in the realm.json file. 2024-07-04 16:40:32 +02:00
			`DEV_USERS = [`
✨(backend) add API access for 'language' attribute on User model - allow the language attribute on the user to be updated via API - add frontend function to update the user language via API - extend defaults on the test users, to have fixed language in E2E tests - extend types and variables using the types with the new field 2025-03-04 14:00:22 +01:00			`{"username": "impress", "email": "impress@impress.world", "language": "en-us"},`
			`{"username": "user-e2e-webkit", "email": "user@webkit.e2e", "language": "en-us"},`
			`{"username": "user-e2e-firefox", "email": "user@firefox.e2e", "language": "en-us"},`
🌱(demo) create dev users and make them doc accesses To be able to test with dummy data, we need to create our dev users from the demo and to give them access to the docs. The sub is the unicity of the user for our oidc provider, so we need to know the sub to be able to create correctly the user, it is why we set the sub as the email of the user in the realm.json file. 2024-07-04 16:40:32 +02:00			`{`
✨(backend) add API access for 'language' attribute on User model - allow the language attribute on the user to be updated via API - add frontend function to update the user language via API - extend defaults on the test users, to have fixed language in E2E tests - extend types and variables using the types with the new field 2025-03-04 14:00:22 +01:00			`"username": "user-e2e-chromium",`
			`"email": "user@chromium.e2e",`
			`"language": "en-us",`
🌱(demo) create dev users and make them doc accesses To be able to test with dummy data, we need to create our dev users from the demo and to give them access to the docs. The sub is the unicity of the user for our oidc provider, so we need to know the sub to be able to create correctly the user, it is why we set the sub as the email of the user in the realm.json file. 2024-07-04 16:40:32 +02:00			`},`
			`]`