Config for extension

Open
#3 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
devops

Research direction

No files, tests, or entry points are named. Start by locating the hardcoded development IPs and the client-side startup path, then determine the intended configuration source and how development environments should consume it. Done means the configuration approach is defined and the random hardcoded values are no longer required.

Written by the indexing model from the issue text.

Description

We don't want to hardcode random IPs and similar things for development environments. How do we manage client-side configuration?

Dominant language
Python
Stars
12
Forks
11
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ArgLab/writing_observer

All issues in ArgLab/writing_observer

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.