ollama-proxy 0.1.0

Proxy server for Ollama
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74

# Contributing to Ollama API Proxy Server

Thank you for considering contributing to Ollama API Proxy Server! Here are some guidelines to help you get started.

## Development Environment Setup

1. Install the Rust toolchain using [rustup](https://rustup.rs/)
2. Clone the repository
3. Build the project with `cargo build`
4. Run tests with `cargo test`

## Code Style

We use the standard Rust formatting style. Before submitting a pull request, please run:

```bash
cargo fmt
cargo clippy
```

Our CI pipeline will verify that your code follows these guidelines.

## Commit Messages

We follow the [Conventional Commits](https://www.conventionalcommits.org/) specification for commit messages. Please read our [CONVENTIONAL_COMMITS.md](CONVENTIONAL_COMMITS.md) guide for details.

This helps keep the commit history clean and generate accurate changelogs.

## Testing

Please add tests for any new features or bug fixes. Run the test suite with:

```bash
cargo test
```

To run all tests, including those that are ignored by default:

```bash
cargo test -- --ignored
```

## Pull Request Process

1. Fork the repository
2. Create a feature branch (`git checkout -b feature/amazing-feature`)
3. Commit your changes using conventional commits format
4. Run the local CI script to verify your changes (`./run-ci.sh`)
5. Push to the branch (`git push origin feature/amazing-feature`)
6. Open a Pull Request using the provided PR template

## Continuous Integration

All pull requests are automatically tested via GitHub Actions. The CI pipeline runs:

- `cargo fmt` to check code formatting
- `cargo clippy` with warnings treated as errors
- `cargo doc` to ensure documentation builds correctly
- `cargo test` to run the test suite

Please make sure these checks pass locally before submitting your PR.

## Feature Flags

The project uses Cargo feature flags to enable optional functionality:

- `database-logging`: Enables logging requests and responses to a SQLite database (enabled by default)

When adding new optional features, please use appropriate feature flags.

## License

By contributing to this project, you agree that your contributions will be licensed under
both the MIT license and the Apache License (Version 2.0)