StreamCore v1.1.2

# How to Install and Update

Recommended path: use the root `install.sh` script for fast Docker deployment. It installs Docker if needed, asks for your configuration, updates `docker-compose.yml`, and starts the full stack.

Open Updates Overview Open Markdown Guide

## Quick Start (install.sh)

1) Run from project root

    chmod +x install.sh
    sudo bash install.sh

2) Choose mode in the menu

- `1) New Installation`: full setup and deployment.
- `2) Update`: rebuild backend/frontend only, keep DB and compose config.

3) Access the app

- Frontend URL and API URL are printed by the script at the end.
- Default admin user: `admin`.
- Admin password: the one you entered during the script prompts.

The script requires root privileges and edits `docker-compose.yml` in place. It creates an automatic backup file like `docker-compose.yml.bak.YYYYMMDD_HHMMSS`.

## What install.sh configures

### Deployment mode

- localhost
- LAN IP
- Domain setup (manual proxy or auto Nginx + Let's Encrypt)

### Core settings

- App name
- PostgreSQL user/password/database
- `JWT_SECRET`
- `ADMIN_DEFAULT_PASSWORD`

### Optional + security

- Stripe keys and currency
- Proxy allowlist and auth requirements
- Proxy private-IP policy
- Automatic backup retention/interval

## Compose commands used by the script

Mode | Command | When used
--- | --- | ---
New install (no proxy) | `docker compose up -d --build` | localhost / IP / manual reverse proxy mode
New install (auto proxy + SSL) | `docker compose --profile proxy up -d --build` | domain mode with automatic Nginx + Let's Encrypt
Update mode | `docker compose build --no-cache backend frontend` `docker compose up -d` | rebuild web/API services without resetting DB

## Daily operations

### Logs

    docker compose logs -f
    docker compose logs -f backend
    docker compose logs -f frontend
    docker compose logs -f postgres

### Restart / stop

    docker compose up -d
    docker compose down

### Full reset (destructive)

    docker compose down -v

This removes volumes and deletes database data.

## Legacy migration path (v1.0.0 SQLite -> v1.1.2 PostgreSQL)

If you are upgrading from old SQLite deployments, use the full migration workflow in HOW_TO_UPDATE.md (backup SQLite, start PostgreSQL stack, and run admin import APIs).