FilOzone / FilOzone/dealbot

dealbot env vars are complicated

Open
#333 1 comment 0 reactions 0 assignees View on GitHub
enhancement needs-triage
Dominant language
TypeScript
Stars
3
Forks
9
Avg merge
4d 14h
Merged PRs (30d)
6

Description

we should probably use a yaml/toml/json config file for configuring dealbot

**NOTE:** There is another tracking issue #118 that talks about setting backend config via front-end.. I think we need a holistic review of configuration/api needs so we can control dealbot config without needing a restart/rollout, and it would also allow filoz leaders to see/change dealbot config via an admin API of some sort. (this would get us out of gitops for config changes but could be useful for hotfix scenarios)

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no files, tests, or entry points. Start by reviewing how dealbot currently receives environment variables and read tracking issue #118 for related backend configuration needs. Done requires an agreed scope for configuration storage, runtime updates, and any admin API rather than an isolated format change.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
backend-api-design, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.