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

Hardcode Requirements into Code/Container instead of fetching them from a URL at start-up #479

Open
vorburger opened this issue Aug 27, 2023 · 0 comments

Comments

@vorburger
Copy link
Contributor

In #477 I have noticed that apparently some ISPs (mine) block https://orchestrator.strn.pl now.

This causes the L1 Node container of this project to fail to start with this following error:

2023-08-27T13:41:42.814Z node@mainnet:registration Initiating registration (initial=true)
2023-08-27T13:41:42.904Z node@mainnet:registration Failed to fetch requirements: FetchError
2023-08-27T13:41:42.905Z node@mainnet Failed to register Error Failed to fetch requirements: FetchError

I suspect that's because https://orchestrator.strn.pl/requirements is blocked.

Might it be more prudent to bake the requirements into the JS code or host the file in the container instead of fetching it from a URL?

Just a thought and for discussion.

@vorburger vorburger changed the title General issue Hardcode Requirements into Code/Container instead of fetching them from a URL at start-up Aug 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant