Skip to content
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.

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

Isolate Connector and prepare it to accept data from the script #60

Closed
2 of 3 tasks
phoenix-web3 opened this issue Jan 13, 2022 · 0 comments · Fixed by #92
Closed
2 of 3 tasks

Isolate Connector and prepare it to accept data from the script #60

phoenix-web3 opened this issue Jan 13, 2022 · 0 comments · Fixed by #92
Assignees
Labels
enhancement New feature or request

Comments

@phoenix-web3
Copy link
Collaborator

phoenix-web3 commented Jan 13, 2022

  • I have read the Contributing file of the documentation.
  • I have searched the issues (including closed ones) and believe that this is not a duplicate.
  • I am willing to lend a hand to help implement this feature.

Feature Request

Feature Description

It is intended to separate the logic of the Connector from the logic of the APIs. For this we need to take the connector out of all docker-composes and make it standalone.

In addition, the Connector should have a new /refresh endpoint where it will receive some parameters from the startup script with which it will change the variables of the connector.py files of each corresponding API.

Finally, the endpoint system will change from http://any_server/rpc to http://any_server/<COIN>/rpc to be able to route requests to the different blockchains from a single instance of the connector.

Use Case(s)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants