everything-dev: proxy

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
typescript
Domain
api, backend

Research direction

Start by tracing the --proxy option and the api.proxy setting, then review how requests, plugins, and provided authentication are connected. Check the context from #150. Done means proxy requests reach the API for the selected client, support the stated default or overrides, and preserve the same-host authentication permissions.

Written by the indexing model from the issue text.

Description

Proxy is broken -- it did have api.proxy would be a url

Enabled by --proxy
Could use domain/api by default, or be override directly in api or in plugins

Unlocked after #150

I expect to be able to proxy requests to this api for that client, using the provided auth -- since same hosts and auth, you can login and have same permissions

Dominant language
TypeScript
Stars
5
Forks
6
Avg merge
1m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

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 NEARBuilders/everything-dev

All issues in NEARBuilders/everything-dev

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.