ecmind-blue-studio 1.0.0a1__tar.gz

ecmind_blue_studio-1.0.0a1/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 ECMind GmbH
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

ecmind_blue_studio-1.0.0a1/PKG-INFO

@@ -0,0 +1,233 @@
+Metadata-Version: 2.4
+Name: ecmind-blue-studio
+Version: 1.0.0a1
+Summary: ECMind blue Studio, admin interface for the ecmind-blue-client
+Author: ECMind GmbH
+Author-email: ECMind GmbH <info@ecmind.ch>
+License-Expression: MIT
+License-File: LICENSE
+Requires-Dist: fastapi
+Requires-Dist: uvicorn
+Requires-Dist: jinja2
+Requires-Dist: pydantic-settings
+Requires-Dist: itsdangerous
+Requires-Dist: python-multipart
+Requires-Dist: ecmind-blue-client==1.0.0
+Requires-Python: >=3.13
+Project-URL: Homepage, https://ecmind.ch/
+Project-URL: Repository, https://gitlab.ecmind.ch/open/ecmind_blue_studio
+Description-Content-Type: text/markdown
+
+# ECMind blue Studio
+
+A admin interface for the DMS enaio(r) (OPTIMAL SYSTEMS GmbH), exposing the 
+ecmind-blue-client features.
+Query folders, registers and documents with a simple query language in a Monaco 
+editor, inspect results and download files. Works fully offline against your
+DMS infrastructure; all frontend assets are vendored.
+
+## Features (work in progress)
+
+- Browser-like vertical tabs, each with a query editor and a result view
+- Object definition explorer: every cabinet, type and index field with its full
+  configuration, a filter over all of it, prefilled statements per object type
+  and the native asobjdef.xml as download
+- Job call monitor: the live server job stream with filters per server, job,
+  computer, application and user, and the full parameters of a single call with
+  base64 payloads decoded
+- Simple query language for folders, registers and documents with subqueries,
+  Klausel-style conditions, code completion and diagnostics
+- Security statements for users, groups, roles, membership and the rights export
+- Result tables per object type with file download
+- ECMind theme with Green/Yellow/Blue brands, automatic light/dark mode
+- English/German localization with automatic detection
+
+## Requirements
+
+- Python >= 3.13 and [uv](https://docs.astral.sh/uv/)
+- A DMS application server (default: 127.0.0.1:4000)
+- A technical account with the system role "Kontextwechsel" (switch context)
+
+## Setup
+
+```
+uv sync
+copy .env.example .env
+# edit .env: servers, technical account, session secret
+```
+
+## Run
+
+```
+uv run uvicorn ecmind_blue_studio.main:app --reload --host 127.0.0.1 --port 8099
+```
+
+Then open http://127.0.0.1:8099 and log in with a DMS user.
+
+## Object definition
+
+The first tab cannot be closed and shows what the DMS server knows about its
+own data model: cabinets with their folders, registers and documents, the index
+mask fields of every type with data type, database column and names in the
+configured languages, and the complete configuration of a single field. The
+filter box searches all of it at once, six buttons per object type open a
+prefilled `select`, `count`, `insert`, `update`, `upsert` or `delete` statement
+in a new tab, and the download button hands out the native `asobjdef.xml`.
+
+It needs the system role "DMS: Supervisor" (18) or "Editor: Starten" (11);
+without one of them the tab is not shown.
+
+## Job calls
+
+The second fixed tab shows the live job stream of the configured servers, the
+same feed the Enterprise Manager displays. Press Listen and every finished job
+appears as one line with its timestamp, computer, user, job name, application
+and file counts; a green check for success, a red warning for a failure, and
+optionally a blue play line when the job starts. Filter by server, by job (a
+popup over every namespace the server offers), by computer, application or user,
+or reduce the stream to failures only. Clicking a line shows the call the way
+the Enterprise Manager prints it, with base64 payloads decoded and XML indented.
+
+It needs the system role "DMS: Supervisor" (18) or "Administrator: Starten" (1).
+The monitor runs on the technical connection, which is why the roles are checked
+on the server and not only in the browser. Job parameters are shown unmasked.
+
+## Query language
+
+Each tab has a Monaco editor with completion, hover and live diagnostics for a
+simple query language (see [SPECS.md](SPECS.md) section 4). Ctrl+Enter runs the
+query, Shift+Alt+F formats it, Alt+N opens a tab and Alt+W closes it. Internal
+field names work without brackets:
+
+```
+select document Invoice, DeliveryNote where Status = 'open' order by InvoiceDate desc limit 100
+select document Invoice in (register Correspondence where Subject = 'Dunning*') where InvoiceNo != ''
+select document Invoice where Clerk = #USER# and InvoiceDate >= #DATE#-1y6m
+select document Invoice columns InvoiceNo, Amount, folder.CompanyName
+select document Invoice columns InvoiceNo, {OBJECT_FILESIZE}, {OBJECT_MODIFYTIME}, {OBJECT_DOCPAGECOUNT}
+count document Invoice where Status = 'open'
+```
+
+System fields (`OBJECT_ID`, `OBJECT_LINKS`, `OBJECT_FILESIZE`, `OBJECT_COUNT`,
+`OBJECT_MODIFYUSER` and more, see SPECS.md) work in `where`, `order by` and
+`columns`; document-only fields are rejected on folder and register queries
+with a live editor marker.
+
+The editor also flags object types the signed-in user cannot see, and completion
+notes them in its list. The DMS answers a query on such a type with an empty result
+and no error at all, so the hint is shown before the run. It stays a warning and
+never blocks the query: a type you can see may return no rows as well.
+
+Data statements update, create and delete objects, always with the rights of the
+signed-in user:
+
+```
+update document Invoice 4711 set Status = 'paid'
+update document Invoice 4711, 4712 set Status = 'paid'
+delete document Invoice 6524, 6522 purge
+insert document Invoice into 55 set InvoiceNo = 'R-9' file 'scan.pdf'
+upsert document Invoice into 55 set InvoiceNo = 'R-9', Amount = 12.5 search InvoiceNo
+variant 4711 set Status = 'draft' file 'v2.pdf'
+delete document Invoice where Status = 'void' purge
+insert document Invoice into 55 set InvoiceNo = 'R-9', Positions = (Article = 'A-100', Qty = 5), (Article = 'B-200', Qty = 3)
+update document Invoice 4711 set Positions = (Article = 'A-100', Qty = 7) replacetables
+```
+
+A single `insert`, `update` or `variant` shows what it wrote: the objects are
+read back from the server and rendered as a result table below the
+confirmation, with the usual row actions. A large `update` (more objects than
+one result page) and statement batches keep the plain confirmation, because
+reading every object back costs a roundtrip each.
+
+Table fields take a comma separated list of rows, each row a list of
+`Column = value` pairs. On update and upsert the statement has to say whether
+the rows replace the table (`replacetables`) or extend it (`appendtables`) -
+the mode belongs to the whole statement, so replacing one table and appending
+to another needs two statements. The table popup in a result row carries an
+"Edit table" button that opens a new tab with exactly such a statement, filled
+with the rows currently stored.
+
+Files referenced by `file '...'` are attached to the tab with the paperclip
+button; `file #BROWSE#` instead opens the file dialog every time the statement
+`update` and `delete` also take a list of object ids, and every listed object
+gets its own copy of the file; a failing object does not stop the others, and
+the result lists what was written and what failed. On an id based update the
+`set` clause is optional, so
+`update document Invoice 6523 file 'scan.pdf'` replaces only the file and
+`update document Invoice 6523 file #NULL#` only removes it. Prefilled
+document statements (edit button, object definition page) end with
+`file #BROWSE#` as a reminder; delete the line for metadata-only changes.
+File content can also be written inline, with an optional extension
+after the closing quotes so the DMS knows the file type: `file '''<data>
+</data>'''.xml` stores the text, `file b64'''iVBOR...'''.png` decodes base64
+(line breaks and spaces are ignored), and `file #NULL#` removes the document
+file on an update. Without an extension, text becomes a txt and base64 a bin
+file:
+
+```
+insert document Invoice into 5693
+  set InvoiceNo = 'R-9'
+  file b64'''
+iVBORw0KGgoAAAANSUhEUgAAABAAAAARCAYAAADUryzE...
+  '''.png;
+select document Invoice
+```
+
+Security statements administer the DMS users, groups and roles in the same
+language, again with the rights of the signed-in user, so the server enforces
+the role for configuring the security system:
+
+```
+select user where locked = false order by username limit 100
+select user where group = 'Sales'
+select group where user = #USER#
+insert user KOL set display_name = 'Roland Koller', password = 'Start.2026', change_pwd = true
+add user KOL to group Sales
+export security group Sales, Marketing
+```
+
+`select user KOL` shows one account with every attribute, `count group` the
+number alone, and `delete user KOL forward to MEY` hands the portfolios and
+mails over before the account goes. User and group rows carry the same edit
+button as DMS rows: it opens a new tab with an `update user` or `update group`
+statement holding the current values. The password is never part of it, and
+never part of a result or a log.
+
+Results render as a table by default or as JSON, JSONL, XML, CSV, TSV or TSV
+quoted, `sql` results included. Every text format opens in an editable editor, so
+the output can be trimmed before copy or download hands it to the next step.
+TSV sanitizes tabs and line breaks inside values to keep one record per line,
+TSV quoted keeps them and quotes like CSV instead. Every result
+row offers details (metadata, variants and versions), an edit button that opens
+a prefilled update statement, and file download.
+
+Statement batches (separated by `;`) stream their results statement by
+statement, report the executed command and the upsert action per row, and can
+be cancelled mid run; the stop button in the toolbar also aborts long running
+queries. A query starting with a comment line names its tab, the question
+button in the toolbar lists all keyboard shortcuts, the info button next to it
+opens the about dialog, and the tab rail shows the connected DMS servers
+above the user menu.
+
+## Tests
+
+```
+uv run pytest                            # unit and endpoint tests
+$env:EBS_LIVE_TESTS = "1"; uv run pytest -m live   # against a local DMS (PowerShell)
+```
+
+## Documentation
+
+- [SPECS.md](SPECS.md) - full specification and decision log
+- [TODO.md](TODO.md) - backlog
+- [CHANGELOG.md](CHANGELOG.md) - notable changes
+
+## License
+
+MIT, see [LICENSE](LICENSE). Bundled third-party libraries, fonts, icons and tools are
+acknowledged in [THIRD-PARTY-NOTICES.md](THIRD-PARTY-NOTICES.md).
+
+The MIT license covers this software only and grants no rights to the DMS itself. Operators must
+make sure their use of the DMS is covered by their own license agreement with the DMS vendor or
+reseller. See the DMS licensing section of
+[THIRD-PARTY-NOTICES.md](THIRD-PARTY-NOTICES.md).

ecmind_blue_studio-1.0.0a1/README.md

@@ -0,0 +1,213 @@
+# ECMind blue Studio
+
+A admin interface for the DMS enaio(r) (OPTIMAL SYSTEMS GmbH), exposing the 
+ecmind-blue-client features.
+Query folders, registers and documents with a simple query language in a Monaco 
+editor, inspect results and download files. Works fully offline against your
+DMS infrastructure; all frontend assets are vendored.
+
+## Features (work in progress)
+
+- Browser-like vertical tabs, each with a query editor and a result view
+- Object definition explorer: every cabinet, type and index field with its full
+  configuration, a filter over all of it, prefilled statements per object type
+  and the native asobjdef.xml as download
+- Job call monitor: the live server job stream with filters per server, job,
+  computer, application and user, and the full parameters of a single call with
+  base64 payloads decoded
+- Simple query language for folders, registers and documents with subqueries,
+  Klausel-style conditions, code completion and diagnostics
+- Security statements for users, groups, roles, membership and the rights export
+- Result tables per object type with file download
+- ECMind theme with Green/Yellow/Blue brands, automatic light/dark mode
+- English/German localization with automatic detection
+
+## Requirements
+
+- Python >= 3.13 and [uv](https://docs.astral.sh/uv/)
+- A DMS application server (default: 127.0.0.1:4000)
+- A technical account with the system role "Kontextwechsel" (switch context)
+
+## Setup
+
+```
+uv sync
+copy .env.example .env
+# edit .env: servers, technical account, session secret
+```
+
+## Run
+
+```
+uv run uvicorn ecmind_blue_studio.main:app --reload --host 127.0.0.1 --port 8099
+```
+
+Then open http://127.0.0.1:8099 and log in with a DMS user.
+
+## Object definition
+
+The first tab cannot be closed and shows what the DMS server knows about its
+own data model: cabinets with their folders, registers and documents, the index
+mask fields of every type with data type, database column and names in the
+configured languages, and the complete configuration of a single field. The
+filter box searches all of it at once, six buttons per object type open a
+prefilled `select`, `count`, `insert`, `update`, `upsert` or `delete` statement
+in a new tab, and the download button hands out the native `asobjdef.xml`.
+
+It needs the system role "DMS: Supervisor" (18) or "Editor: Starten" (11);
+without one of them the tab is not shown.
+
+## Job calls
+
+The second fixed tab shows the live job stream of the configured servers, the
+same feed the Enterprise Manager displays. Press Listen and every finished job
+appears as one line with its timestamp, computer, user, job name, application
+and file counts; a green check for success, a red warning for a failure, and
+optionally a blue play line when the job starts. Filter by server, by job (a
+popup over every namespace the server offers), by computer, application or user,
+or reduce the stream to failures only. Clicking a line shows the call the way
+the Enterprise Manager prints it, with base64 payloads decoded and XML indented.
+
+It needs the system role "DMS: Supervisor" (18) or "Administrator: Starten" (1).
+The monitor runs on the technical connection, which is why the roles are checked
+on the server and not only in the browser. Job parameters are shown unmasked.
+
+## Query language
+
+Each tab has a Monaco editor with completion, hover and live diagnostics for a
+simple query language (see [SPECS.md](SPECS.md) section 4). Ctrl+Enter runs the
+query, Shift+Alt+F formats it, Alt+N opens a tab and Alt+W closes it. Internal
+field names work without brackets:
+
+```
+select document Invoice, DeliveryNote where Status = 'open' order by InvoiceDate desc limit 100
+select document Invoice in (register Correspondence where Subject = 'Dunning*') where InvoiceNo != ''
+select document Invoice where Clerk = #USER# and InvoiceDate >= #DATE#-1y6m
+select document Invoice columns InvoiceNo, Amount, folder.CompanyName
+select document Invoice columns InvoiceNo, {OBJECT_FILESIZE}, {OBJECT_MODIFYTIME}, {OBJECT_DOCPAGECOUNT}
+count document Invoice where Status = 'open'
+```
+
+System fields (`OBJECT_ID`, `OBJECT_LINKS`, `OBJECT_FILESIZE`, `OBJECT_COUNT`,
+`OBJECT_MODIFYUSER` and more, see SPECS.md) work in `where`, `order by` and
+`columns`; document-only fields are rejected on folder and register queries
+with a live editor marker.
+
+The editor also flags object types the signed-in user cannot see, and completion
+notes them in its list. The DMS answers a query on such a type with an empty result
+and no error at all, so the hint is shown before the run. It stays a warning and
+never blocks the query: a type you can see may return no rows as well.
+
+Data statements update, create and delete objects, always with the rights of the
+signed-in user:
+
+```
+update document Invoice 4711 set Status = 'paid'
+update document Invoice 4711, 4712 set Status = 'paid'
+delete document Invoice 6524, 6522 purge
+insert document Invoice into 55 set InvoiceNo = 'R-9' file 'scan.pdf'
+upsert document Invoice into 55 set InvoiceNo = 'R-9', Amount = 12.5 search InvoiceNo
+variant 4711 set Status = 'draft' file 'v2.pdf'
+delete document Invoice where Status = 'void' purge
+insert document Invoice into 55 set InvoiceNo = 'R-9', Positions = (Article = 'A-100', Qty = 5), (Article = 'B-200', Qty = 3)
+update document Invoice 4711 set Positions = (Article = 'A-100', Qty = 7) replacetables
+```
+
+A single `insert`, `update` or `variant` shows what it wrote: the objects are
+read back from the server and rendered as a result table below the
+confirmation, with the usual row actions. A large `update` (more objects than
+one result page) and statement batches keep the plain confirmation, because
+reading every object back costs a roundtrip each.
+
+Table fields take a comma separated list of rows, each row a list of
+`Column = value` pairs. On update and upsert the statement has to say whether
+the rows replace the table (`replacetables`) or extend it (`appendtables`) -
+the mode belongs to the whole statement, so replacing one table and appending
+to another needs two statements. The table popup in a result row carries an
+"Edit table" button that opens a new tab with exactly such a statement, filled
+with the rows currently stored.
+
+Files referenced by `file '...'` are attached to the tab with the paperclip
+button; `file #BROWSE#` instead opens the file dialog every time the statement
+`update` and `delete` also take a list of object ids, and every listed object
+gets its own copy of the file; a failing object does not stop the others, and
+the result lists what was written and what failed. On an id based update the
+`set` clause is optional, so
+`update document Invoice 6523 file 'scan.pdf'` replaces only the file and
+`update document Invoice 6523 file #NULL#` only removes it. Prefilled
+document statements (edit button, object definition page) end with
+`file #BROWSE#` as a reminder; delete the line for metadata-only changes.
+File content can also be written inline, with an optional extension
+after the closing quotes so the DMS knows the file type: `file '''<data>
+</data>'''.xml` stores the text, `file b64'''iVBOR...'''.png` decodes base64
+(line breaks and spaces are ignored), and `file #NULL#` removes the document
+file on an update. Without an extension, text becomes a txt and base64 a bin
+file:
+
+```
+insert document Invoice into 5693
+  set InvoiceNo = 'R-9'
+  file b64'''
+iVBORw0KGgoAAAANSUhEUgAAABAAAAARCAYAAADUryzE...
+  '''.png;
+select document Invoice
+```
+
+Security statements administer the DMS users, groups and roles in the same
+language, again with the rights of the signed-in user, so the server enforces
+the role for configuring the security system:
+
+```
+select user where locked = false order by username limit 100
+select user where group = 'Sales'
+select group where user = #USER#
+insert user KOL set display_name = 'Roland Koller', password = 'Start.2026', change_pwd = true
+add user KOL to group Sales
+export security group Sales, Marketing
+```
+
+`select user KOL` shows one account with every attribute, `count group` the
+number alone, and `delete user KOL forward to MEY` hands the portfolios and
+mails over before the account goes. User and group rows carry the same edit
+button as DMS rows: it opens a new tab with an `update user` or `update group`
+statement holding the current values. The password is never part of it, and
+never part of a result or a log.
+
+Results render as a table by default or as JSON, JSONL, XML, CSV, TSV or TSV
+quoted, `sql` results included. Every text format opens in an editable editor, so
+the output can be trimmed before copy or download hands it to the next step.
+TSV sanitizes tabs and line breaks inside values to keep one record per line,
+TSV quoted keeps them and quotes like CSV instead. Every result
+row offers details (metadata, variants and versions), an edit button that opens
+a prefilled update statement, and file download.
+
+Statement batches (separated by `;`) stream their results statement by
+statement, report the executed command and the upsert action per row, and can
+be cancelled mid run; the stop button in the toolbar also aborts long running
+queries. A query starting with a comment line names its tab, the question
+button in the toolbar lists all keyboard shortcuts, the info button next to it
+opens the about dialog, and the tab rail shows the connected DMS servers
+above the user menu.
+
+## Tests
+
+```
+uv run pytest                            # unit and endpoint tests
+$env:EBS_LIVE_TESTS = "1"; uv run pytest -m live   # against a local DMS (PowerShell)
+```
+
+## Documentation
+
+- [SPECS.md](SPECS.md) - full specification and decision log
+- [TODO.md](TODO.md) - backlog
+- [CHANGELOG.md](CHANGELOG.md) - notable changes
+
+## License
+
+MIT, see [LICENSE](LICENSE). Bundled third-party libraries, fonts, icons and tools are
+acknowledged in [THIRD-PARTY-NOTICES.md](THIRD-PARTY-NOTICES.md).
+
+The MIT license covers this software only and grants no rights to the DMS itself. Operators must
+make sure their use of the DMS is covered by their own license agreement with the DMS vendor or
+reseller. See the DMS licensing section of
+[THIRD-PARTY-NOTICES.md](THIRD-PARTY-NOTICES.md).

ecmind_blue_studio-1.0.0a1/pyproject.toml

@@ -0,0 +1,61 @@
+[project]
+name = "ecmind-blue-studio"
+version = "1.0.0a1"
+description = "ECMind blue Studio, admin interface for the ecmind-blue-client"
+readme = "README.md"
+requires-python = ">=3.13"
+license = "MIT"
+license-files = ["LICENSE"]
+dependencies = [
+    "fastapi",
+    "uvicorn",
+    "jinja2",
+    "pydantic-settings",
+    "itsdangerous",
+    "python-multipart",
+    "ecmind-blue-client==1.0.0",
+]
+
+[[project.authors]]
+name = "ECMind GmbH"
+email = "info@ecmind.ch"
+
+[project.urls]
+Homepage = "https://ecmind.ch/"
+Repository = "https://gitlab.ecmind.ch/open/ecmind_blue_studio"
+
+[project.scripts]
+ecmind-blue-studio = "ecmind_blue_studio.__main__:main"
+
+[dependency-groups]
+dev = [
+    "pytest",
+    "pytest-asyncio",
+    "pytest-cov",
+    "httpx",
+    "ruff",
+]
+
+[build-system]
+requires = ["uv_build>=0.11,<0.13"]
+build-backend = "uv_build"
+
+[tool.pytest.ini_options]
+markers = ["live: needs a local DMS instance"]
+addopts = "-m 'not live'"
+asyncio_mode = "auto"
+
+[tool.ruff]
+line-length = 120
+src = [
+    "src",
+    "tests",
+]
+
+[tool.ruff.lint]
+ignore = [
+    "DTZ001",
+    "DTZ005",
+    "DTZ006",
+    "DTZ011",
+]

ecmind_blue_studio-1.0.0a1/pyproject.toml.orig

@@ -0,0 +1,51 @@
+[project]
+name = "ecmind-blue-studio"
+version = "1.0.0a1"
+description = "ECMind blue Studio, admin interface for the ecmind-blue-client"
+readme = "README.md"
+requires-python = ">=3.13"
+license = "MIT"
+license-files = ["LICENSE"]
+authors = [{ name = "ECMind GmbH", email = "info@ecmind.ch" }]
+dependencies = [
+    "fastapi",
+    "uvicorn",
+    "jinja2",
+    "pydantic-settings",
+    "itsdangerous",
+    "python-multipart",
+    "ecmind-blue-client==1.0.0",
+]
+
+[dependency-groups]
+dev = [
+    "pytest",
+    "pytest-asyncio",
+    "pytest-cov",
+    "httpx",
+    "ruff",
+]
+
+[project.urls]
+Homepage = "https://ecmind.ch/"
+Repository = "https://gitlab.ecmind.ch/open/ecmind_blue_studio"
+
+[project.scripts]
+ecmind-blue-studio = "ecmind_blue_studio.__main__:main"
+
+[build-system]
+requires = ["uv_build>=0.11,<0.13"]
+build-backend = "uv_build"
+
+[tool.pytest.ini_options]
+markers = ["live: needs a local DMS instance"]
+addopts = "-m 'not live'"
+asyncio_mode = "auto"
+
+[tool.ruff]
+line-length = 120
+src = ["src", "tests"]
+
+[tool.ruff.lint]
+# DMS index data and query variables use naive server-local datetimes.
+ignore = ["DTZ001", "DTZ005", "DTZ006", "DTZ011"]

ecmind_blue_studio-1.0.0a1/src/ecmind_blue_studio/__init__.py

@@ -0,0 +1,3 @@
+"""ECMind blue Studio, a web client for the DMS."""
+
+__version__ = "1.0.0a1"

ecmind_blue_studio-1.0.0a1/src/ecmind_blue_studio/__main__.py

@@ -0,0 +1,18 @@
+"""Entry point: run the web client with uvicorn."""
+
+
+def main() -> None:
+    import uvicorn
+
+    from ecmind_blue_studio.config import get_settings
+
+    settings = get_settings()
+    uvicorn.run(
+        "ecmind_blue_studio.main:app",
+        host=settings.host,
+        port=settings.port,
+    )
+
+
+if __name__ == "__main__":
+    main()