HTTP Daemon Custom IPNI Endpoint Flag #409
Comments
jtsmedley
added a commit
to jtsmedley/lassie
that referenced
this issue
Sep 7, 2023
Closes filecoin-project#409 by adding the IPNI Endpoint Flag to the Daemon and adds a positive/negative test for the flag on the daemon. Adding the positive/negative test required changing the exit command on 119 of daemon.go to pass the err on up. Please review and confirm this won't introduce any unintentional side effects.
rvagg
pushed a commit
that referenced
this issue
Sep 7, 2023
Closes #409 by adding the IPNI Endpoint Flag to the Daemon and adds a positive/negative test for the flag on the daemon. Adding the positive/negative test required changing the exit command on 119 of daemon.go to pass the err on up. Please review and confirm this won't introduce any unintentional side effects.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We currently have no flag to set a custom endpoint for IPNI lookups when launched with
lassie daemon. This flag is essential to be able to run Lassie with it's own indexstar endpoint and is a flag already when usinglassie fetch --ipni-endpoint https://cid.contact(https://github.com/filecoin-project/lassie/blob/main/cmd/lassie/fetch.go#L65).The text was updated successfully, but these errors were encountered: