Install chirpstack-rest-api v4 via apt install?

[datnus]

Hi all,
For ChirpStack v4, could we make something to install chirpstack-rest-api v4 via ‘sudo apt install chirpstack-rest-api’ in Ubuntu?
Or the only way to install is to build from source?

ChirpStack-rest-API: GitHub - chirpstack/chirpstack-rest-api: ChirpStack gRPC API to REST proxy.

Thanks a lot for your effort.

[martin]

Or maybe release package like with chirpstack-v3-to-v4 tool may be nicer, so you can just wget, unpack and install the service with pre-compiled binary?

[brocaar]

Yes, that is the plan but I didn’t have time yet to integrate this properly in the build and release pipeline

[datnus]

Let me try to build in Ubuntu.
The instruction seems for Docker.
Thanks a lot.

[fromnowhereuser]

Hello,

I have issue when i try to compile the package.

Cant build

[IvanP]

Hello,
can you put step by step instruction for built on ubuntu, because when I try to build get error on every line that can find ./Makefile: line 30: go: command not found
./Makefile: line 32: devshell:: command not found …

Thank you

[tiib]

go: command not found seems like you do not have go installed or in your path.

The best way in my opinion to run or build the api is to use the docker-container and access it with make devshell

Inside the container you can then call the build command for example.

[brocaar]

For apt install ... documentation, please see: GitHub - chirpstack/chirpstack-rest-api: ChirpStack gRPC API to REST proxy.

For downloading pre-compiled binaries, see: Index of /downloads/chirpstack-rest-api/.

[datnus]

Awesome.
Let me test the REST API at weekend.
Thanks a lot for your great effort.

[datnus]

Tested.
Working perfectly.
Just need to take note some parameters or endpoint urls or json format may change compared to v3.

The script for NGINX proxy.

location /rest-api/ {
    proxy_pass http://localhost:8090/;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "Upgrade";
    proxy_read_timeout 86400s;
    proxy_send_timeout 86400s;
}