Files
omsorg/omsorgapp/README.md
T
Felix KemmlerandClaude Sonnet 5 b6c1389c55 Reorganize into monorepo layout, move mitarbeiter-app to legacy reference
Consolidates the previously separate omsorgapp and omsorgCore repos
(each had their own nested .git with GitHub history) plus the old
root-level website/mitarbeiter-app into a single monorepo, matching
the structure already documented in the root CLAUDE.md. Also moves
the PHP employee app aside as omsorgWeb/mitarbeiter-app-legacy/ to
serve as a template for a ground-up rewrite.

Fixes .gitignore in the same pass: the config-secrets/uploads/data
patterns were unanchored (relative to repo root, not depth-agnostic),
so they silently stopped matching once the app moved under omsorgWeb/.
Patterns are now **/-prefixed and cover both mitarbeiter-app and
mitarbeiter-app-legacy, keeping DB/SMTP credentials and uploaded
employee documents out of version control.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-08-07 14:21:37 +02:00

25 lines
727 B
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Omsorg Business Controls Pro Release 0.1.1 Foundation
Stabile lokale Electron/React-Basis ohne native SQLite-Abhängigkeit.
## Warum 0.1.1?
Release 0.1.0 nutzte `better-sqlite3`. Auf macOS/Electron kann dieses native Modul Versionsprobleme verursachen.
Release 0.1.1 speichert Daten zuerst in einer lokalen JSON-Datenbank im Benutzerordner.
## Start
```bash
cd ~/Desktop/omsorg-business-controls-pro-release-0.1.1
npm install
npm run dev
```
## Lokale Daten
Die App legt Ordner unter `~/Documents/Omsorg Business Controls Pro` an:
- database/omsorg-local-db.json
- documents/employees
- documents/customers
- backups
## Nächster Sprint
SQLite wird später sauber über eine entkoppelte Persistenzschicht eingebaut.