Skip to content

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

@vorburger

Description

@vorburger

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions