Skip to content

adds bifrost ui #111

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
akshaydeo wants to merge 1 commit into from
Closed

adds bifrost ui #111

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,3 +5,7 @@
**/venv/
**/__pycache__/**
private.*

# Build artifacts
tmp/
*.log
128 changes: 128 additions & 0 deletions Makefile
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,128 @@
# Makefile for Bifrost

# Variables
CONFIG_FILE ?= transports/config.example.json
PORT ?= 8080
POOL_SIZE ?= 300
PLUGINS ?= maxim
PROMETHEUS_LABELS ?=

# Colors for output
RED=\033[0;31m
GREEN=\033[0;32m
YELLOW=\033[1;33m
BLUE=\033[0;34m
CYAN=\033[0;36m
NC=\033[0m # No Color

.PHONY: help dev dev-ui build run install-air clean test ui-dev ui-build ui-install

# Default target
help: ## Show this help message
@echo "$(BLUE)Bifrost Development - Available Commands:$(NC)"
@echo ""
@grep -E '^[a-zA-Z_-]+:.*?## .*$$' $(MAKEFILE_LIST) | sort | awk 'BEGIN {FS = ":.*?## "}; {printf " $(GREEN)%-15s$(NC) %s\n", $$1, $$2}'
@echo ""
@echo "$(YELLOW)Environment Variables:$(NC)"
@echo " CONFIG_FILE Path to config file (default: transports/config.example.json)"
@echo " PORT Server port (default: 8080)"
@echo " POOL_SIZE Connection pool size (default: 300)"
@echo " PLUGINS Comma-separated plugins to load (default: maxim)"
@echo " PROMETHEUS_LABELS Labels for Prometheus metrics"

install-air: ## Install air for hot reloading (if not already installed)
@which air > /dev/null || (echo "$(YELLOW)Installing air for hot reloading...$(NC)" && go install github.com/air-verse/air@latest)
@echo "$(GREEN)Air is ready$(NC)"

dev: ui-install install-air ## Start complete development environment (UI + API with proxy)
@echo "$(GREEN)Starting Bifrost complete development environment...$(NC)"
@echo "$(YELLOW)This will start:$(NC)"
@echo " 1. UI development server (localhost:3000)"
@echo " 2. API server with UI proxy (localhost:$(PORT)/ui)"
@echo "$(CYAN)Access everything at: http://localhost:$(PORT)/ui$(NC)"
Comment thread
coderabbitai[bot] marked this conversation as resolved.
@echo ""
@echo "$(YELLOW)Starting UI development server...$(NC)"
@cd ui && npm run dev &
@sleep 3
Comment on lines +45 to +46

@coderabbitai coderabbitai Bot Jun 22, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Add cleanup mechanism for background processes

The npm run dev & starts a background process but lacks cleanup if the make target fails or is interrupted. Consider adding a trap to kill background processes on exit.

 @echo "$(YELLOW)Starting UI development server...$(NC)"
+@trap 'kill %1 2>/dev/null || true' EXIT
 @cd ui && npm run dev &
 @sleep 3
🤖 Prompt for AI Agents 
In the Makefile around lines 54 to 55, the background process started by `npm
run dev &` lacks a cleanup mechanism. Add a trap command before starting the
background process to ensure that if the make target fails or is interrupted,
the background process is killed. This involves capturing the process ID of the
background job and using a trap to kill it on script exit or interruption.

@echo "$(YELLOW)Starting API server with UI proxy...$(NC)"
@cd transports/bifrost-http && BIFROST_UI_DEV=true air -c .air.toml -- \
-config "../../$(CONFIG_FILE)" \
-port "$(PORT)" \
-pool-size $(POOL_SIZE) \
-plugins "$(PLUGINS)" \
$(if $(PROMETHEUS_LABELS),-prometheus-labels "$(PROMETHEUS_LABELS)")

build: ## Build bifrost-http binary
@echo "$(GREEN)Building bifrost-http...$(NC)"
@cd transports/bifrost-http && go build -o ../../tmp/bifrost-http .
@echo "$(GREEN)Built: tmp/bifrost-http$(NC)"

run: build ## Build and run bifrost-http (no hot reload)
@echo "$(GREEN)Running bifrost-http...$(NC)"
@./tmp/bifrost-http \
-config "$(CONFIG_FILE)" \
-port "$(PORT)" \
-pool-size $(POOL_SIZE) \
-plugins "$(PLUGINS)" \
$(if $(PROMETHEUS_LABELS),-prometheus-labels "$(PROMETHEUS_LABELS)")


clean: ## Clean build artifacts and temporary files
@echo "$(YELLOW)Cleaning build artifacts...$(NC)"
@rm -rf tmp/
@rm -f transports/bifrost-http/build-errors.log
@rm -rf transports/bifrost-http/tmp/
@echo "$(GREEN)Clean complete$(NC)"

test: ## Run tests for bifrost-http
@echo "$(GREEN)Running bifrost-http tests...$(NC)"
@cd transports/bifrost-http && go test -v ./...

test-core: ## Run core tests
@echo "$(GREEN)Running core tests...$(NC)"
@cd core && go test -v ./...

test-plugins: ## Run plugin tests
@echo "$(GREEN)Running plugin tests...$(NC)"
@cd plugins && find . -name "*.go" -path "*/tests/*" -o -name "*_test.go" | head -1 > /dev/null && \
for dir in $$(find . -name "*_test.go" -exec dirname {} \; | sort -u); do \
echo "Testing $$dir..."; \
cd $$dir && go test -v ./... && cd - > /dev/null; \
done || echo "No plugin tests found"

Comment on lines +85 to +92

@coderabbitai coderabbitai Bot Jun 21, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

⚠️ Potential issue

Plugin test detection fallback is ineffective
head -1 always exits successfully, so the "No plugin tests found" branch never runs when there are no tests. This hides missing test feedback.
Apply this diff to fix the logic:

@@ -85,8 +85,15 @@ test-plugins: ## Run plugin tests
-	@cd plugins && find . -name "*.go" -path "*/tests/*" -o -name "*_test.go" | head -1 > /dev/null && \
-		for dir in $$(find . -name "*_test.go" -exec dirname {} \; | sort -u); do \
+	@cd plugins && \
+	if find . -name "*.go" -path "*/tests/*" -o -name "*_test.go" | grep -q .; then \
+		for dir in $$(find . -name "*_test.go" -exec dirname {} \; | sort -u); do \
 			echo "Testing $$dir..."; \
 			cd $$dir && go test -v ./... && cd - > /dev/null; \
-		done || echo "No plugin tests found"
+		done; \
+	else \
+		echo "No plugin tests found"; \
+	fi
🤖 Prompt for AI Agents 
In the Makefile around lines 85 to 92, the current plugin test detection uses
'head -1' which always exits successfully, preventing the "No plugin tests
found" message from appearing when no tests exist. To fix this, modify the logic
to properly check if any test files are found before running tests, ensuring the
fallback message is triggered when no tests are present. Adjust the command so
that it fails or returns a non-zero exit code when no test files are found,
enabling the fallback echo statement to run.

test-all: test-core test-plugins test ## Run all tests

# Quick start with example config
quick-start: ## Quick start with example config and maxim plugin
@echo "$(GREEN)Quick starting Bifrost with example configuration...$(NC)"
@$(MAKE) dev CONFIG_FILE=transports/config.example.json PLUGINS=maxim

# Docker targets
docker-build: ## Build Docker image
@echo "$(GREEN)Building Docker image...$(NC)"
@cd transports && docker build -t bifrost .
@echo "$(GREEN)Docker image built: bifrost$(NC)"

docker-run: ## Run Docker container
@echo "$(GREEN)Running Docker container...$(NC)"
@docker run -p $(PORT):$(PORT) \
-v $(PWD)/$(CONFIG_FILE):/app/config/config.json \
--env-file <(env | grep -E '^(OPENAI|ANTHROPIC|AZURE|AWS|COHERE|VERTEX)_') \
bifrost

Comment on lines +106 to +112

@coderabbitai coderabbitai Bot Jun 21, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

⚠️ Potential issue

Process substitution breaks in POSIX shell
--env-file <(env | ...) requires Bash; /bin/sh invoked by Make won’t support it.
Proposed fix:

@@ -133,5 +133,8 @@ docker-run: ## Run Docker container
-	@docker run -p $(PORT):$(PORT) \
-		-v $(PWD)/$(CONFIG_FILE):/app/config/config.json \
-		--env-file <(env | grep -E '^(OPENAI|ANTHROPIC|AZURE|AWS|COHERE|VERTEX)_') \
-		bifrost
+	@bash -c 'docker run -p $(PORT):$(PORT) \
+		-v $(PWD)/$(CONFIG_FILE):/app/config/config.json \
+		--env-file <(env | grep -E "^(OPENAI|ANTHROPIC|AZURE|AWS|COHERE|VERTEX)_") \
+		bifrost'
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
docker-run: ## Run Docker container
@echo "$(GREEN)Running Docker container...$(NC)"
@docker run -p $(PORT):$(PORT) \
-v $(PWD)/$(CONFIG_FILE):/app/config/config.json \
--env-file <(env | grep -E '^(OPENAI|ANTHROPIC|AZURE|AWS|COHERE|VERTEX)_') \
bifrost
docker-run: ## Run Docker container
@echo "$(GREEN)Running Docker container...$(NC)"
@bash -c 'docker run -p $(PORT):$(PORT) \
-v $(PWD)/$(CONFIG_FILE):/app/config/config.json \
--env-file <(env | grep -E "^(OPENAI|ANTHROPIC|AZURE|AWS|COHERE|VERTEX)_") \
bifrost'
🤖 Prompt for AI Agents 
In the Makefile at lines 133 to 139, the use of process substitution with
--env-file <(env | grep ...) breaks in POSIX shells because /bin/sh does not
support it. To fix this, replace the process substitution by creating a
temporary environment file before running the docker command, write the filtered
environment variables to that file, and then pass the file path to --env-file.
Clean up the temporary file after the docker run completes.

# Linting and formatting
lint: ## Run linter for Go code
@echo "$(GREEN)Running golangci-lint...$(NC)"
@golangci-lint run ./...

fmt: ## Format Go code
@echo "$(GREEN)Formatting Go code...$(NC)"
@gofmt -s -w .
@goimports -w .
Comment on lines +119 to +121

@coderabbitai coderabbitai Bot Jun 22, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Verify goimports availability

The fmt target assumes goimports is installed, but it's not a standard Go tool and may not be available in all environments.

 fmt: ## Format Go code
 	@echo "$(GREEN)Formatting Go code...$(NC)"
 	@gofmt -s -w .
-	@goimports -w .
+	@if command -v goimports > /dev/null 2>&1; then \
+		goimports -w .; \
+	else \
+		echo "$(YELLOW)goimports not found, skipping import formatting$(NC)"; \
+	fi
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
@echo "$(GREEN)Formatting Go code...$(NC)"
@gofmt -s -w .
@goimports -w .
fmt: ## Format Go code
@echo "$(GREEN)Formatting Go code...$(NC)"
@gofmt -s -w .
@if command -v goimports > /dev/null 2>&1; then \
goimports -w .; \
else \
echo "$(YELLOW)goimports not found, skipping import formatting$(NC)"; \
fi
🤖 Prompt for AI Agents 
In the Makefile around lines 164 to 166, the fmt target uses the goimports
command without verifying its availability, which may cause failures if
goimports is not installed. Add a check before running goimports to verify it is
installed, and if not, either print a warning or install it automatically. This
ensures the fmt target runs reliably across different environments.


# Git hooks and development setup
setup-git-hooks: ## Set up Git hooks for development
@echo "$(GREEN)Setting up Git hooks...$(NC)"
@echo "#!/bin/sh\nmake fmt\nmake lint" > .git/hooks/pre-commit
@chmod +x .git/hooks/pre-commit
@echo "$(GREEN)Git hooks installed$(NC)"
Comment on lines +124 to +128

@coderabbitai coderabbitai Bot Jun 21, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick (assertive)

Consider centralizing Git hooks
Writing directly to .git/hooks may override custom user hooks. Consider using a .githooks/ directory and git config core.hooksPath .githooks.

🤖 Prompt for AI Agents 
In the Makefile around lines 151 to 155, the current setup writes Git hooks
directly to .git/hooks, which can overwrite existing user hooks. Modify the
setup to create a .githooks directory if it doesn't exist, place the pre-commit
hook script there, and configure Git to use this directory by running git config
core.hooksPath .githooks. This approach centralizes hooks and avoids overwriting
user customizations.

53 changes: 53 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -169,6 +169,7 @@ For additional HTTP server configuration options, read [this](https://github.com
- [ii) OR Using Docker](#ii-or-using-docker)
- [B. Using Bifrost as a Go Package](#b-using-bifrost-as-a-go-package)
- [📑 Table of Contents](#-table-of-contents)
- [🛠️ Development](#️-development)

@coderabbitai coderabbitai Bot Jun 22, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick (assertive)

Fix Table of Contents anchor for Development section.

The link [🛠️ Development](#️-development) uses an incorrect anchor and will not jump to the new section. Update it to match the heading slug (for example, [#🛠️-development](#🛠️-development) or simply [#development](#development)).

🤖 Prompt for AI Agents 
In README.md at line 172, the Table of Contents link for the Development section
uses an incorrect anchor `#️-development` that does not match the heading slug.
Update the link to use a correct anchor such as `#🛠️-development` or
`#development` to ensure it properly jumps to the Development section.

- [🔍 Overview](#-overview)
- [✨ Features](#-features)
- [🏗️ Repository Structure](#️-repository-structure)
Expand All @@ -186,6 +187,52 @@ For additional HTTP server configuration options, read [this](https://github.com

---

## 🛠️ Development

Bifrost includes a comprehensive development environment with hot reloading and build tools.

### Quick Start

```bash
# Set up development environment
make dev-full

# Complete development environment (UI dev server + API with proxy)
make dev-ui

# Or start API server only with static UI files
make dev
```
Comment on lines +190 to +205

@coderabbitai coderabbitai Bot Jun 22, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick (assertive)

Add blank line before fenced code block and update ToC subentries.

There’s no blank line between the ### Quick Start heading and the fenced code block—add one for proper Markdown rendering. Also consider adding “Quick Start” (and perhaps “Available Commands” / “Environment Variables”) as subentries under the new Development section in the ToC.

🤖 Prompt for AI Agents 
In README.md around lines 190 to 205, add a blank line between the "### Quick
Start" heading and the fenced code block to ensure proper Markdown rendering.
Additionally, update the Table of Contents by adding "Quick Start" as a subentry
under the "Development" section, and consider including "Available Commands" and
"Environment Variables" as subentries as well.


### Available Commands

Use `make help` to see all available commands:

| Command | Description |
|--------------|--------------------------------------------------|
| `dev` | Start bifrost-http with hot reload using Air |
| `dev-ui` | Start complete development environment (UI + API) |
| `build` | Build bifrost-http binary |
| `run` | Build and run bifrost-http (no hot reload) |
| `test-all` | Run all tests (core, plugins, transports) |
| `ui-build` | Build UI for production (static export) |
| `docker-build` | Build Docker image |
| `lint` | Run Go linter |
| `fmt` | Format Go code |

### Environment Variables

- `CONFIG_FILE`: Path to config file (default: `transports/config.example.json`)
Comment thread
coderabbitai[bot] marked this conversation as resolved.
- `PORT`: Server port (default: `8080`)
- `PLUGINS`: Comma-separated plugins to load (default: `maxim`)

**Example:**
```bash
make dev CONFIG_FILE=my-config.json PORT=3000 PLUGINS=maxim,other
```
Comment on lines +229 to +232

@coderabbitai coderabbitai Bot Jun 22, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick (assertive)

Ensure blank lines around the Example code block.

Add a blank line before and after the fenced block under Example: so it renders cleanly in Markdown.

🤖 Prompt for AI Agents 
In README.md around lines 229 to 232, the fenced code block under the
**Example:** heading lacks blank lines before and after it, which can cause
rendering issues in Markdown. Add a blank line immediately before the ```bash
line and another blank line immediately after the closing ``` line to ensure
proper formatting and clean rendering.


---

## 🔍 Overview

Bifrost acts as a bridge between your applications and multiple AI providers (OpenAI, Anthropic, Amazon Bedrock, Mistral, Ollama, etc.). It provides a consistent API while handling:
Expand All @@ -212,6 +259,7 @@ With Bifrost, you can focus on building your AI-powered applications without wor
- **MCP Integration**: Built-in Model Context Protocol (MCP) support for external tool integration and execution
- **Custom Configuration**: Offers granular control over pool sizes, network retry settings, fallback providers, and network proxy configurations
- **Built-in Observability**: Native Prometheus metrics out of the box, no wrappers, no sidecars, just drop it in and scrape
- **Web Interface**: Modern React-based UI for configuration management and monitoring

---

Expand All @@ -236,6 +284,11 @@ bifrost/
│ ├── bifrost-http/ # HTTP transport implementation
│ └── ...
│
├── ui/ # Modern React-based web interface
│ ├── app/ # Next.js 15 application with App Router
│ ├── components/ # Reusable UI components
│ └── ...
│
└── plugins/ # Plugin Implementations
├── maxim/
└── ...
Expand Down
17 changes: 17 additions & 0 deletions transports/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,7 @@ This package contains clients for various transports that can be used to spin up

- [Bifrost Transports](#bifrost-transports)
- [📑 Table of Contents](#-table-of-contents)
- [🛠️ Development](#️-development)
- [🚀 Setting Up Transports](#-setting-up-transports)
- [Prerequisites](#prerequisites)
- [Configuration](#configuration)
Expand All @@ -26,6 +27,22 @@ This package contains clients for various transports that can be used to spin up

---

## 🛠️ Development

For development with hot reloading and comprehensive tooling, use the main Makefile at the repository root:

- **HTTP Transport**: See [`bifrost-http/README.md`](bifrost-http/README.md) for development setup details
- **UI Interface**: See [`../ui/README.md`](../ui/README.md) for React UI development

Comment on lines +34 to +36

@coderabbitai coderabbitai Bot Jun 22, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick (assertive)

Avoid acronym tautology in documentation.
Rename "UI Interface" to simply "UI" or "UI Transport" to prevent redundancy ("Interface" in "UI" already stands for "User Interface").

🧰 Tools
🪛 LanguageTool

[style] ~35-~35: This phrase is redundant (‘I’ stands for ‘Interface’). Use simply “UIInterface”.
Context: ...E.md) for development setup details - UI Interface: See [../ui/README.md](../ui/README...

(ACRONYM_TAUTOLOGY)

🤖 Prompt for AI Agents 
In transports/README.md around lines 34 to 36, rename the heading or label "UI
Interface" to either "UI" or "UI Transport" to avoid redundant wording, since
"UI" already means "User Interface." Update the text accordingly to maintain
clarity without repeating "Interface."

Quick start for HTTP transport development:
```bash
cd .. # Go to repository root
make dev-full # Set up environment
make dev # Start with hot reload
```
Comment on lines +37 to +42

@coderabbitai coderabbitai Bot Jun 22, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick (assertive)

Include UI development command in Quick Start.
Add make ui-dev after make dev to start the UI development server alongside the HTTP transport for a complete development workflow.

🤖 Prompt for AI Agents 
In transports/README.md around lines 37 to 42, the Quick Start section lacks the
command to start the UI development server. Add the command `make ui-dev`
immediately after `make dev` in the code block to instruct users to start the UI
development server alongside the HTTP transport for a complete development
workflow.


Comment on lines +30 to +43

@coderabbitai coderabbitai Bot Jun 22, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick (assertive)

Include UI development command in Quick Start.

To streamline onboarding, add the make ui-dev target alongside the HTTP transport commands:

- Quick start for HTTP transport development:
+ Quick start for development:
  ```bash
  cd ..            # Go to repo root
  make dev-full    # Setup environment
  make dev         # Start HTTP server with hot reload
+ make ui-dev      # Start UI development server

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[style] ~35-~35: This phrase is redundant (‘I’ stands for ‘Interface’). Use simply “UIInterface”.
Context: ...E.md) for development setup details - **UI Interface**: See [`../ui/README.md`](../ui/README...

(ACRONYM_TAUTOLOGY)

</details>
<details>
<summary>🪛 markdownlint-cli2 (0.17.2)</summary>

38-38: Fenced code blocks should be surrounded by blank lines
null

(MD031, blanks-around-fences)

</details>

</details>

<details>
<summary>🤖 Prompt for AI Agents</summary>

In transports/README.md between lines 30 and 43, the Quick Start section for
development only includes commands for HTTP transport but omits the UI
development command. Add the command "make ui-dev" after "make dev" in the Quick
Start bash snippet to include starting the UI development server, improving
onboarding clarity.


</details>

<!-- This is an auto-generated comment by CodeRabbit -->

<!-- fingerprinting:phantom:triton:mountainlion -->

---

## 🚀 Setting Up Transports

### Prerequisites
Expand Down
44 changes: 44 additions & 0 deletions transports/bifrost-http/.air.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,44 @@
root = "."
testdata_dir = "testdata"
tmp_dir = "tmp"

[build]
args_bin = []
bin = "./tmp/main"
cmd = "go build -o ./tmp/main ."
delay = 1000
exclude_dir = ["assets", "tmp", "vendor", "testdata", "node_modules", "out", ".git", ".next"]
exclude_file = []
exclude_regex = ["_test.go"]
exclude_unchanged = false
follow_symlink = false
full_bin = ""
include_dir = [".", "../../core", "../../plugins"]
include_ext = ["go", "tpl", "tmpl", "html"]
include_file = []
kill_delay = "0s"
log = "build-errors.log"
poll = false
poll_interval = 0
rerun = false
rerun_delay = 500
send_interrupt = false
stop_on_root = false

[color]
app = ""
build = "yellow"
main = "magenta"
runner = "green"
watcher = "cyan"

[log]
main_only = false
time = false

[misc]
clean_on_exit = false

[screen]
clear_on_rebuild = false
keep_scroll = true
25 changes: 25 additions & 0 deletions transports/bifrost-http/.gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
# Air (hot reload) temporary files
tmp/
build-errors.log

# Build artifacts
bifrost-http
main
Comment on lines +6 to +7

@coderabbitai coderabbitai Bot Jun 22, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick (assertive)

Optional: add Windows-specific build artifacts
If you produce cross-platform binaries, consider ignoring patterns like *.exe or *.dll.

🤖 Prompt for AI Agents 
In transports/bifrost-http/.gitignore around lines 6 to 7, the file currently
does not ignore Windows-specific build artifacts. To improve cross-platform
compatibility, add ignore patterns for common Windows binaries such as '*.exe'
and '*.dll' to the .gitignore file.


# OS generated files
.DS_Store
.DS_Store?
._*
.Spotlight-V100
.Trashes
ehthumbs.db
Thumbs.db

# IDE
.vscode/
.idea/
*.swp
*.swo

# Logs
*.log
Loading