allucanget/ai.allucanget.biz
2
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Refactor Nginx configuration and update project dependencies

Browse Source 
- Cleaned up the Nginx configuration for the Coolify deployment, ensuring proper formatting and organization.
- Updated the `pyproject.toml` file to maintain consistent formatting.
- Reformatted the `requirements.txt` file for better readability while keeping the dependencies unchanged.
This commit is contained in:
zwitschi committed 2026-09-03 15:05:27 +02:00
1 parent 3b8c30c289
commit a4b874598d
88 files changed
+9766 -9766
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

docs/03-context-and-scope.md
+26 -26
View File
@@ -1,26 +1,26 @@
# 3. Context and Scope
Delimits your system (i.e. your scope) from all its communication partners (neighboring systems and users, i.e. the context of your system). It thereby specifies the external interfaces.
## Business Context
Specification of **all** communication partners (users, IT-systems, …) with explanations of domain specific inputs and outputs or interfaces.
The system exposes REST APIs for authentication, user management, and AI generation. The Flask frontend consumes these APIs and serves pages at `http://ai.allucanget.biz`.
| Communication Partner | Input | Output |
| --------------------- | ------------------------------ | ------------------------------ |
| End User (browser) | Form submissions, API requests | Generated text, images, videos |
| openrouter.ai API | Prompt + model selection | AI-generated content |
| DuckDB | SQL queries | User data, session data |
## Technical Context
| Channel | Protocol | Description |
| -------------------------------- | ---------- | ------------------ |
| User ↔ Flask frontend | HTTPS | Browser-based UI |
| Flask frontend ↔ FastAPI backend | HTTP REST | Internal API calls |
| FastAPI backend ↔ openrouter.ai | HTTPS REST | AI model inference |
| FastAPI backend ↔ DuckDB | In-process | Embedded DB access |
**Mapping Input/Output to Channels:** All user-facing traffic flows through HTTPS. The backend communicates with openrouter.ai over HTTPS. DuckDB is accessed in-process with no network channel.
# 3. Context and Scope
Delimits your system (i.e. your scope) from all its communication partners (neighboring systems and users, i.e. the context of your system). It thereby specifies the external interfaces.
## Business Context
Specification of **all** communication partners (users, IT-systems, …) with explanations of domain specific inputs and outputs or interfaces.
The system exposes REST APIs for authentication, user management, and AI generation. The Flask frontend consumes these APIs and serves pages at `http://ai.allucanget.biz`.
| Communication Partner | Input | Output |
| --------------------- | ------------------------------ | ------------------------------ |
| End User (browser) | Form submissions, API requests | Generated text, images, videos |
| openrouter.ai API | Prompt + model selection | AI-generated content |
| DuckDB | SQL queries | User data, session data |
## Technical Context
| Channel | Protocol | Description |
| -------------------------------- | ---------- | ------------------ |
| User ↔ Flask frontend | HTTPS | Browser-based UI |
| Flask frontend ↔ FastAPI backend | HTTP REST | Internal API calls |
| FastAPI backend ↔ openrouter.ai | HTTPS REST | AI model inference |
| FastAPI backend ↔ DuckDB | In-process | Embedded DB access |
**Mapping Input/Output to Channels:** All user-facing traffic flows through HTTPS. The backend communicates with openrouter.ai over HTTPS. DuckDB is accessed in-process with no network channel.