- Clone repo
git submodule initgit submodule update --remote --recursivePlease use V2 version of docker compose if possible
5. docker compose --profile [with selected services (see compose file)] up -d 6. docker compose watch *for development only
cd .\thesis-backend\At this point, just to make sure everything is up-to-date run commands:
git submodule initgit submodule update --remote --recursive
cd .\thesis-sensors-py-service\python -m venv venvvenv/Scripts/activatepip install -r requirements.txt- Run commands:
-
python -m grpc_tools.protoc -I ./protos --python_out=. --grpc_python_out=. sensor.proto -
python -m grpc_tools.protoc -I ./protos --python_out=. --grpc_python_out=. user.proto -
python -m grpc_tools.protoc -I ./protos --python_out=. --grpc_python_out=. workout.proto
cd ../..docker compose --profile all up --buildto run base services
Optional:
- Create
.envfile in the root folder and paste this:COMPOSE_PROFILES=allThen save, and from now on you can use a regulardocker compose up --buildwithout specifying the profile
If it still won't work message @MxPy or @iraszewska
Use the docker compose command to bring up services associated with the core profile:
docker compose --profile core up
Whole traffic regarding admin panel is routed by the gateway now, but this still can be useful in terms of developing the sensors data related backend.
C4 Architecture diagram is in Documentation folder you can render it here: https://structurizr.com/dsl