Modifying AS files

Hi everyone,

Im trying to make some modification to the AS file.
After building the project and pushing the compiled file to the application server container, the project collapse immediately after the restarting the container.
Im getting this :
chirpstack-network-server_1 | time=“2021-06-24T14:26:22.276705219Z” level=info msg=“signal received” signal=terminated
chirpstack-network-server_1 | time=“2021-06-24T14:26:22.276786203Z” level=warning msg=“stopping chirpstack-network-server”
chirpstack-network-server_1 | time=“2021-06-24T14:26:22.276807565Z” level=info msg=“gateway/mqtt: closing backend”
chirpstack-network-server_1 | time=“2021-06-24T14:26:22.276812952Z” level=info msg=“gateway/mqtt: unsubscribing from event topic” topic=gateway/+/event/+
chirpstack-network-server_1 | time=“2021-06-24T14:26:22.276975444Z” level=info msg=“backend/gateway: handling last messages”
chirpstack-network-server_1 | time=“2021-06-24T14:26:22.276988214Z” level=info msg=“uplink: waiting for pending actions to complete”
mosquitto_1 | 1624544782: Client auto-8020BCFA-3A30-E62C-968D-96F0D2DD0BCE closed its connection.
chirpstack-docker_chirpstack-network-server_1 exited with code 0

The project that Im trying to build is clean without any changes.
after running make clean make build I got :

Building ui

chirpstack-application-server-ui@3.0.0 build
react-scripts build

Creating an optimized production build…
Compiled successfully.

File sizes after gzip:

474.73 KB build/static/js/2.1f2e1503.chunk.js
53.46 KB build/static/js/main.e82d3d58.chunk.js
23.75 KB build/static/css/2.b3235429.chunk.css
791 B build/static/js/runtime-main.4f63df10.js
116 B build/static/css/main.3f9ef032.chunk.css

The project was built assuming it is hosted at /.
You can control this with the homepage field in your package.json.

The build folder is ready to be deployed.
You may serve it with a static server:

npm install -g serve
serve -s build

Find out more about deployment here:

Deployment | Create React App

Fetching Swagger definitions and generate combined Swagger JSON
Cloning into ‘/tmp/chirpstack-api’…
remote: Enumerating objects: 4245, done.
remote: Counting objects: 100% (639/639), done.
remote: Compressing objects: 100% (260/260), done.
remote: Total 4245 (delta 336), reused 594 (delta 313), pack-reused 3606
Receiving objects: 100% (4245/4245), 2.97 MiB | 6.45 MiB/s, done.
Resolving deltas: 100% (2664/2664), done.
Note: checking out ‘v3.10.0’.

You are in ‘detached HEAD’ state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

git checkout -b

HEAD is now at b1bc1ce Refactor multicast groups APIs.
mkdir -p build
go build -ldflags “-s -w -X main.version=51797bd” -o build/chirpstack-application-server cmd/chirpstack-application-server/main.go

After running : make dev-requirements ui-requirements
I got :

go mod download
go install The Go Programming Language
go install The Go Programming Language
go install GitHub - goreleaser/goreleaser: Deliver Go binaries as fast and easily as possible
go install GitHub - goreleaser/nfpm: nFPM is Not FPM - a simple deb, rpm, apk and arch linux packager written in Go
go install github.com/golang/protobuf/protoc-gen-go
go install github.com/golang-migrate/migrate/v4/cmd/migrate
Installing UI requirements

up to date, audited 2010 packages in 6s

155 packages are looking for funding
run npm fund for details

22 vulnerabilities (9 moderate, 13 high)

To address issues that do not require attention, run:
npm audit fix

To address all issues (including breaking changes), run:
npm audit fix --force

Run npm audit for details.

Thanks :slight_smile:

I managed to solve the problem by building the project from docker itself :slight_smile:

Hi Ibrahim,

Can you please decribe the steps you have taken, because i am facing the same issue at you.

With me, I am also unable to compile it in the docker environment