Stream: warg

Topic: Local warg deployment

view this post on Zulip Paul Scheduikat (Jan 15 2024 at 15:35):

I'm trying to get the registry to work locally, as far as I understand after using the local Infra setup the registry should be running on "http://127.0.0.1:17513"

This seems to be the case:

tcp        0      0 127.0.0.1:17513         0.0.0.0:*               LISTEN      79789/docker-proxy
tcp        0      0 127.0.0.1:17514         0.0.0.0:*               LISTEN      33839/docker-proxy

However when trying to publish an example package I get this:

$ warg config --registry http://127.0.0.1:17513
$ warg key new 127.0.0.1:17513
$ warg publish init example:hello
error: failed to send request to registry server: error sending request for url (http://127.0.0.1:17513/v1/package/sha256:071fda594d2219ee6a4b8fb7deb6e10f01a6dcf4890f2c120c973e5b0fe134d3/record): connection error: Connection reset by peer (os error 104)

I'm a bit lost here, any pointers?

view this post on Zulip Calvin Prewitt (Jan 15 2024 at 16:29):

These directions are the ones that should work for you: https://github.com/bytecodealliance/registry/blob/main/crates/server/README.md

Sorry for the confusion. I don't think the local infra instructions work.

view this post on Zulip 趙子賢 (Danny Chao) (May 12 2024 at 13:40):

I have submitted a pull request to the repo. Can anyone help reviewing that?
https://github.com/bytecodealliance/registry/pull/282

Fix docker compose error and improve developer experience by ZhaoTzuHsien · Pull Request #282 · bytecodealliance/registry
After discussion with @calvinrp, we reached a consensus that improving the local development experience and documentation is important to make more developer participate in this project. This pull ...

Last updated: Dec 23 2024 at 12:05 UTC