Dev version - no default login admin possible

Report a Bug
1

Configuration: Debian 12.12, MongoDB 7, Datagerry Development Binary as of 2025-03-21
Connection using HTTPS with Apache2 as reverse proxy

With the current Development version from Git repo (2025-03-21) if I start the assembled binary
WITHOUT an preexisting cmdb database it gives me the following error:

…
[2025-03-21 13:08:16][INFO ] — [SETUP ROUTINE] Pre create (setup_routine.py)
[2025-03-21 13:08:16][ERROR ] — [setup] Exception: Working outside of application context.

This typically means that you attempted to use functionality that needed
the current application. To solve this, set up an application context
with app.app_context(). See the documentation for more information.. Type: <class ‘RuntimeError’> (setup_routine.py)
[2025-03-21 13:08:16][ERROR ] — Something went wrong during the generation of the user management.
Error: Working outside of application context.

This typically means that you attempted to use functionality that needed
the current application. To solve this, set up an application context
with app.app_context(). See the documentation for more information. (main.py)
[2025-03-21 13:08:16][WARNING ] — The setup did not go through as expected - Status SetupStatus.ERROR (main.py)

–
Then it is NOT possible to login with the usual default credentials admin/admin.
If I try for comparison via the release version (2.2.0) no login is possible either.

If I remove the cmdb database, let it be created by Datagerry (release) version 2.2.0 and then use the developer version login is possible.

So it seems the creation of the initial database seems to be dysfunctional in the current development version besides the CSV-import (see my other ticket for the latter)

2

Hi @cmdbeval1,
this issue is known and will probably fixed in the next week. since we were focusing on the cloud version of datagerry the on premise version has now some flask context issues. But thanks for the feedback.

BR Adnan

1 Like
3

Hi @cmdbeval1 ,
the login and database creation should be fixed with the latest dev build. Let us know if you still exerience any issues.

BR Adnan

4

Hi,

  1. New database with current dev (2025-04-03) WORKS NOW in my environment
    (Debian12 + Mongo 7)

  2. For the other reported problem (List view user setting column) if I modify
    the columns to display and try to save I get the following error (see below)
    in the debug console
    Environment: see above, using my OLD database and trying to save column
    settings for standard type “Client” with only 1 minimum client (1 textline
    filled) just created