-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
None
Context:
Currently the frontend devs always have to restart the whole dev environment (this includes elasticsearch, cambpm & another data generation run) when they pull latest optimize backend changes. This is not always necessary, at least cambpm or even elasticsearch could stay and only the backend could be rebuild and restarted to incorporate most compatible changes.
AT:
- there is a way to just rebuild/restart the optimize backend leaving cambpm and elasticsearch untouched
Hint:
This was raised by omran.abazeed in doubt ask him on more details.