mirror of
https://github.com/jeffusion/gitea-ai-assistant.git
synced 2026-03-27 10:05:50 +00:00
Update all documentation to reflect new global LOG_LEVEL environment variable. - Add LOG_LEVEL to configuration reference tables - Update deployment guides with LOG_LEVEL=error examples - Clarify dev (info) vs production (error) log level recommendations - Add LOG_LEVEL to all .env examples and quick start guides Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent)
70 lines
1.3 KiB
Markdown
70 lines
1.3 KiB
Markdown
# Getting Started
|
|
|
|
## Prerequisites
|
|
|
|
- Bun >= 1.2.5
|
|
- A reachable Gitea instance
|
|
- At least one LLM provider credential
|
|
|
|
## Install
|
|
|
|
```bash
|
|
git clone https://github.com/user/gitea-ai-assistant.git
|
|
cd gitea-ai-assistant
|
|
bun install
|
|
```
|
|
|
|
`bun install` at repository root installs frontend dependencies via `postinstall`.
|
|
|
|
If lifecycle scripts are disabled:
|
|
|
|
```bash
|
|
bun run bootstrap
|
|
```
|
|
|
|
## Minimal environment
|
|
|
|
Create `.env`:
|
|
|
|
```bash
|
|
PORT=5174
|
|
ENCRYPTION_KEY= # required, generate with: openssl rand -hex 32
|
|
# DATABASE_PATH=./data/assistant.db
|
|
# LOG_LEVEL=info # local dev default; use LOG_LEVEL=error in production
|
|
```
|
|
|
|
> `ENCRYPTION_KEY` is required. Application startup fails when it is missing.
|
|
|
|
## Run
|
|
|
|
```bash
|
|
bun run dev
|
|
# or
|
|
bun run start
|
|
```
|
|
|
|
## First login
|
|
|
|
- Open `http://your-server:5174`
|
|
- Default admin password is `password` on first boot
|
|
- Change admin password immediately after login
|
|
|
|
## Webhook setup
|
|
|
|
### Option A: Admin UI (recommended)
|
|
|
|
In repository list, click enable to auto-provision webhook.
|
|
|
|
### Option B: Manual
|
|
|
|
In Gitea repository settings:
|
|
|
|
- URL: `http://your-server:5174/webhook/gitea`
|
|
- Content Type: `application/json`
|
|
- Secret: same value as dashboard webhook secret
|
|
- Events: Pull Request + Status
|
|
|
|
## Health endpoint
|
|
|
|
Use `/api/health` to check service status.
|