Building chirpstack server from source using docker-compose

shubham1996 · December 23, 2021, 7:11am

Dear community,

I am new in docker. I tried building from source using docker-compose. I followed the following steps:

step 1: Download the chirpstack network server, application server and gateway bridge zip files from github.
step 2: Unzip them in Home directory
step 3: Get inside the chirpstack-gateway-bridge-master directory and run the command docker-compose run --rm chirpstack-gateway-bridge bash
step 4: Get inside the chirpstack-network-server-master directory and run the command docker-compose run --rm chirpstack-network-server bash
step 5: Get inside the chirpstack-application-server directory and run the command docker-compose run --rm chirpstack-application-server bash
Following containers are running on my system:

Screenshot from 2021-12-15 17-47-53

I am unable to access the chirpstack-application-server web interface. Did I complete all of the processes correctly, or do some more steps need to be completed? kindly help.

Actually I want to modify the ADR algorithm and I could not do it with ADR plugin option. The documentation is really good but steps needed to work with ADR plugin should have been given in more detail, as many people are facing issues.

chopmann · December 23, 2021, 9:25am

Just a hint when you are compiling something you don’t know, look at the “CI-Files”.

github.com

brocaar/chirpstack-application-server/blob/master/.github/workflows/main.yml

name: CI
on:
  push:
    branches:
      - '*'
    tags:
      - 'v*'
  pull_request:

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      -
        name: Checkout
        uses: actions/checkout@v2
      -
        name: Install UI depdencies
        run: docker-compose run --rm chirpstack-application-server make ui-requirements
      -

This file has been truncated. show original

github.com

brocaar/chirpstack-application-server/blob/master/Makefile

.PHONY: build clean test ui-requirements serve statics
VERSION := $(shell git describe --always |sed -e "s/^v//")
API_VERSION := $(shell go list -m -f '{{ .Version }}' github.com/brocaar/chirpstack-api/go/v3 | awk '{n=split($$0, a, "-"); print a[n]}')

build: ui/build static/swagger/api.swagger.json
	mkdir -p build
	go build $(GO_EXTRA_BUILD_ARGS) -ldflags "-s -w -X main.version=$(VERSION)" -o build/chirpstack-application-server cmd/chirpstack-application-server/main.go

clean:
	@echo "Cleaning up workspace"
	@rm -rf build dist internal/static/static_gen.go ui/build static/static
	@rm -f static/index.html static/icon.png static/manifest.json static/asset-manifest.json static/service-worker.js
	@rm -rf static/logo
	@rm -rf static/integrations
	@rm -rf static/swagger/*.json
	@rm -rf dist

test: statics
	@echo "Running tests"
	@rm -f coverage.out

This file has been truncated. show original

The CI/CD pipeline does mostly what you want in an automated way. It’s always a good place to understand which requirements you need.